We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For archival packages created with Archivematica there is a well defined format (https://www.archivematica.org/en/docs/archivematica-1.7/user-manual/archival-storage/aip-structure/) and metadata is readily identified from the METS file. What conventions should be used for packages created via other routes and what should be the algorithm for finding metadata within them?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
For archival packages created with Archivematica there is a well defined format (https://www.archivematica.org/en/docs/archivematica-1.7/user-manual/archival-storage/aip-structure/) and metadata is readily identified from the METS file. What conventions should be used for packages created via other routes and what should be the algorithm for finding metadata within them?
The text was updated successfully, but these errors were encountered: