SLAC Persistent Archives Testbed Project
Metadata Discussions

General Discussions

10/25/2005 Antoine DeTorcy asked about levels of metadata: do we want to structure it hierarchically? 10/27/2005 Wilko Kroeger pointed out that the SRB hierarchy is Collection, Container, File. Jean Deken commented that the archival hierarchy has typically been Repository, Collection, Accession, Container, File. (Once again, we are using the same words, but meaning different things. In the SRB the Collection has a structure: you can have a directory structure within a collection, the collection has levels that are also called collection, until you get to the file level, which is called "file." You get different levels, but the hierarchy is a placement hierarchy, and not necessarily an intellectual hierarchy. It can be an intellectual hierarchy, but it does not have to be. Given this fact, using the SRB hierarchy to structure the metadata may not be workable.

We think that this topic is ripe for further discussion with the SDSC folks: perhaps we need to have our metadata in a separate table that is linked in some way to the items in the SRB?

11/1/05. Jean: Accession-level metadata applies to an accession (intellectually unified group of electronic records ingested at the same time). Accession-level metadata should be associated with the accession, and could be placed in a metadata table (like the current SLAC collections database, SLACARC. To see sample records, look at the results of a search on Richter under Physicist). Item-level metadata applies to an individual item, and should be associated, linked with the item. I have updated the list below to indicate which items should be accession-level, and which items should be item-level.

Attribute-Level Discussions

Injected Metadata

9/15/05: Each object, or each collection has its own metadata. If you have groups that consist of many files and collections . Perhaps we should have our own database tables that link to SRB objects, that give layers. SLAC's metadata database would mediate between the user and the SRB. User won't know the difference, it will be transparent to the user. Layers of metadata for SLAC objects, some (injected) metadata applies to ALL entities. Tricky part is to define the structure of the tables. Could use a template for individual groups of records (ex. SLD, BaBar).

  1. : Record Group

    Level: Accession-level metadata
    Discussion: 434 is the NARA record group number for the US Department of Energy. Other numbers may be appropriate for use for future accessions of records from SLAC.

  2. : Responsible federal agency

    Level:Accession-level metadata
    Discussion: For the SLD records, this is the Department of Energy. In the future, this could be a different funding agency, like NASA (National Aeronautics and Space Administration) or NIH (National Institutes of Health).

  3. : Reference provided by

    Level: Accession-level metadata
    Discussion: This metadata attribute is derived from the NARA LCDRG (Life-Cycle Data Requirements Guide). Right now we are using the SLAC Archives & History Office information: once the records have been transferred to NARA, contact information for the cognizant NARA unit will go here.

  4. : Applicable records control schedule

    Level: Accession-level metadata
    Discussion: This attribute uses the record series description and schedule citation from the authorized government records control schedule. For the SLD records, the applicable schedule is online and the relevant items are linked to each series on the SLC Records Descriptions page.

  5. : Series within the applicable records control schedule to which the records belong.

    Level: Series/Accession-level metadata
    Discussion: Series name from the authorized government records control schedule.

  6. : Official series description

    Level: Series/Accession-level metadata
    Discussion: Exact wording of series description from the authorized government records control schedule. In future, this will help to pull together same series records from different experiments or laboratories. Since we are using the exact wording in the government schedule, it may be possible to add data for this attribute automatically?

  7. : Period of time accession should be retained

    Level: Accession-level metadata
    Discussion: The retention period is prescribed by the applicable government records control schedule item. Sample values for this attribute:

    • Permanent, Offer to Archives 01/2029
    • Retain until 10/2015
    • Review 01/2009
  8. slac.creator.organization: Creating Organization

    Level: Accession-level metadata
    Discussion: This is the top-level of the creating organization, so, for the SLD project this attribute value is SLAC.

  9. slac.creator.division : Creating Division at SLAC

    Level: Accession-level metadata
    Discussion: For the SLD project, the creating division at SLAC is the Research Division, or RD.

  10. : Creating Group at SLAC

    Level: Accession-level metadata
    This metadata element could contain the group description from the SPIRES Experiments database: either the narrative description or a link to the description. The downside of having a link is that we do not control the Experiments database and in the past old entries have been deleted. It might be easier to copy over also, because we will only need this metadata element content once. (Actually, the old Experiments db content is on a server at SLAC, it is just not web-accessible at the moment.)

  11. slac.description.type : Type of archival description

    Level: Accession-level metadata
    Discussion: At SLAC, for records retired to NARA, the description type will always be "Series."

  12. : Description author

    Level: Accession-level metadata
    Discussion: The name of the person who provided the injected metadata is added here, in the format of Lastname, Firstname. This is a repeatable attribute. Might want to link to

  13. : Date description was completed

    Level: Accession-level metadata
    Discussion: Date that metadata was completed or last revised. Repeatable attribute.

  14. slac.description.remarks : Additional information about the accession

    Level: Accession-level metadata
    Discussion: Used only if there is some additional information needed.

  15. slac.identifier.copy : Type of copy this is

    Level: Accession-level metadata
    Discussion: For the SLD project, all of the copy types are "Preservation". Other types could be: Reference, Duplicate, Original (?)

  16. slac.identifier.contmgt : Content Management System

    Level: Accession-level metadata
    Discussion: The name and version of a content management system that may have been used to manage files on the web. Required by NARA ( NARA WCG 6.4.7 ). If no content management system was used, this attribute will be left out of the metadata set.

  17. slac.identifier.websitename : Name of Web Site

    Level: Accession-level metadata
    Discussion: Generally found on the home or index page of a web site, generally a header on that page. Might be able to extract automatically? Required by NARA ( NARA WCG 6.4.2 )

  18. slac.capture.tool : Tool used to capture/crawl website

    Level: Accession-level metadata
    Discussion: According to NARA WCG 6.4.5: "include the application used with either a URL to the application's web site or a description of the harvester's capabilities and the log file(s) generated by the harvester that document the harvesting process."

  19. slac.capture.settings : Settings used on capture/crawl tool

    Level: Accession-level metadata
    Discussion:Information required by NARA WCG 6.4.5. Format will be determined by tool used.

  20. slac.capture.sitemap : Sitemap of captured/crawled site

    Level: Accession-level metadata
    Discussion: Include if available (if created by crawl tool), per NARA WCG 6.4.10.

  21. : Date capture/crawl of website accomplished

    Level: Accession-level metadata
    Discussion: Information required by NARA WCG 6.4.5.

  22. : Person who accomplished capture/crawl of website

    Level: Accession-level metadata
    Discussion: Information required by NARA WCG 6.4.6. Format is Lastname, Firstname. Email address, telephone number. (Repeatable attribute?)

  23. slac.capture.remarks : Remarks about capture/crawl of website

    Level: Accession-level metadata
    Discussion: Use this attribute, if necessary, to record additional information about capture/crawl.

  24. slac.pawn.recordset

    Level: Accession-level metadata
    Discussion: Record Set is a PAWN convention that allows the user to establish a link or relationship between more than 1 item or group of items BOTH as they are in transit AND after they have been submitted.

  25. < a name="pawncat" href="MetadataSchem8.html">slac.pawn.category

    Level" Accession-level metadata
    Discussion: Category is the PAWN equivalent of a Record Series

Extracted Metadata

  1. : Access restriction(s)

    Level: Accession-level metadata
    Discussion: Access restriction can be prescribed by the government records schedule, or by the creator/creating group at SLAC. Options for this item are: Open, Restricted, or Restricted until xxx.

  2. slac.creator.person : Individual responsible for creating the entity.

    Level: Item-level metadata
    Discussion: Format as Lastname, Firstname. Should be able to extract from pages. Should be repeatable attribute, since more than one person's name can be associated with an electronic entity.

  3. slac.creator.owner : Owner

    Level: Item-level metadata
    Discussion: Individual named as owner of the entity, if different from the creator

  4. slac.description.local : SLAC-generated narrative description of records

    Level: Accession-level metadata
    Discussion: What the records series or web site is called at SLAC, as opposed to what the official government records schedule series description calls it.

  5. slac.description.use : Is research use allowed at this time?

    Discussion: Attribute is either yes (use is allowed) or no (use is not allowed at this time). Jean 10/19/2005: For all of the PAT project SLD records series, this value should be set to "yes". For future projects, this value will probably need to be injected, based on the archivist's appraisal of the records series. Unless a tool could be created to establish this attribute based on the value of the attribute?

  6. slac.description.webplatform: Web Platform

  7. : Beginning date

    Level: Item-level metadata

  8. : Date last modified

    Level: Item-level metadata

  9. slac.identifier.url : Original url for record/resource

    Level: Item-level metadata

  10. slac.identifier.filename : Original filename

    Level: Item-level metadata

  11. slac.description.format :

    Level: Item-level metadata

  12. slac.description.filesize :

    Level: Item-level metadata

  13. slac.identifier.storagelocation : Storage location of the copy being described

    Level: Item-level or Accession-level metadata??

    11/1/05: Question from Jean--will a SLAC-identified accession be stored in the same location on the SRB, or will the location metadata need to be item-level metadata?

  14. slac.identifier.persistent : Persistent identifier

    Level: Item-level metadata

Articles and References

Updated: 25 April 2007 J.M. Deken

Valid XHTML 1.0 Strict