Archival METS
From UA Libraries Digital Services Planning and Documentation
(Difference between revisions)
(New page: IDS) |
|||
| (One intermediate revision not shown.) | |||
| Line 1: | Line 1: | ||
| + | Given that we've standardized our file and directory names, and are ordering our files so that information about a file or set of files resides at the level to which it applies, it's simply a matter of logic to create METS files out of our materials. | ||
| + | Example of content in a directory: | ||
| + | [[image:Slide0033_image147.png]] | ||
| - | [[IDS]] | + | |
| + | The problem of what to name the identifiers within the METS file which refer to each type of file and where it connects is addressed in [[IDS]]. | ||
| + | |||
| + | Although our current archiving system does not require METS wrappers for each item, we are mindful that the future may hold something very different in store. :-) | ||
| + | |||
| + | Currently, it looks like that future may involve the [http://d-p-n.org/ Digital Preservation Network]. | ||
Current revision
Given that we've standardized our file and directory names, and are ordering our files so that information about a file or set of files resides at the level to which it applies, it's simply a matter of logic to create METS files out of our materials.
Example of content in a directory:
The problem of what to name the identifiers within the METS file which refer to each type of file and where it connects is addressed in IDS.
Although our current archiving system does not require METS wrappers for each item, we are mindful that the future may hold something very different in store. :-)
Currently, it looks like that future may involve the Digital Preservation Network.
