[Esip-preserve] OAIS RM Audits and Collection Structure

[Nancy Hoebelheinrich]

Hi, Bruce:

Of those standards you mentioned, I would think that either PREMIS or METS
would tie more closely to an inventory of items in an Earth science archive,
and those probably would do so somewhat indirectly.  To my knowledge, FRBR
is used more as the basis for the kind of description that would be used in
a search & discovery system at a higher level, and as such, may or may not
include ALL items in an archive.  METS has the capability of acting as a
collection data structure because of its capability for grouping items,
i.e., files primarily, and associating all kinds of contextual metadata
about those files and about the groupings, but I suspect it is used less for
the purposes of straight inventorying and more for aggregating the metadata
and navigating through groupings to display the items, etc.  The event
"entity" in PREMIS (rather than "object" in PREMIS' terms since there is
also an object entity) would probably be used for processes that are used on
the data within an archive with the effective necessity of associating a
linkingObjectIdentifier to the event.  The object to which the event is
linked must have an identifier unique to the archive or repository, but
could have more than one identifier to account for both internally and
externally assigned identifiers.  By this mechanism, I would think PREMIS
could be used as an inventory system for an archive as well, although I
think it more likely that it would be used as a supplement or complement to
a more robust inventory system.  I'm not a storage expert for repositories
by any means, but I suspect that scale and the ease of retrieving inventory
information might be an issue for either PREMIS or METS because of the fact
that they're expressed in XML (at least at this point - both are moving
toward RDF as another expression of the schemas).   And, given that is not
the primary purpose for either one of them, perhaps that's just the way it
is, ma'am, or should I say "Sir!"  The repositories / archives with which
I've had experience assign UUIDs to any item in their archive that they wish
to track, and that ID is used for inventorying / managing purposes.  The
assigned UUID would show up in other systems that needed to reference,
retrieve or call upon the item.  

 

Hope this makes sense / helps.

Nancy

 

 

 <https://kmotifs.com/> _LOGOhiResTRANSPARENT_4800pxRGB

 

Nancy J. Hoebelheinrich

Information Analyst/Principal

nhoebel at kmotifs.com

San Mateo, CA  94401

(v) 650-302-4493

(f) 650-745-3333

 

From: esip-preserve-bounces at lists.esipfed.org
[mailto:esip-preserve-bounces at lists.esipfed.org] On Behalf Of Bruce
Barkstrom
Sent: Sunday, May 26, 2013 1:11 PM
To: ESIP Preservation cluster
Subject: [Esip-preserve] OAIS RM Audits and Collection Structure

 

If you haven't run into it before, you might want to get a copy of
CCSDS 652.0-M-1 Audit and Certification of Trustworthy Repositories
(which is also ISO 16363:2011, although this probably lies outside the
boundaries of the groups dealing with the ISO 19115 and related
geospatial standards).  Just Google CCSDS 652-0-M-1 and the
first reference should be the pdf for this document.

One question that comes to mind is how to keep track of the
inventory of items in an Earth science archive.  I'm inclined to think
that a data structure that can encompass the collection structures
we're encountering would also be able to serve as a kind of backbone
for an inventory that would assist in auditing the preservation approaches
of an archive.  If you look at 652.0-M-1, you'll also see that it encourages
keeping records of custodianship - who authorized events that affect
the inventory and who actually implemented those actions.  I'm not
sure whether or not the event "objects" in some of the library standards,
such as FRBR specifically tie to an inventory.  Can someone familiar
with those particular standards (including PREMIS or METS) comment?

Bruce B.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.esipfed.org/pipermail/esip-preserve/attachments/20130528/c66fd509/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: application/octet-stream
Size: 9711 bytes
Desc: not available
URL: <http://www.lists.esipfed.org/pipermail/esip-preserve/attachments/20130528/c66fd509/attachment.obj>