Configure Metadata

 

Process Module: Manage Entity

Process Title: Configure Metadata

Definition: Process where metadata is normalized and processed according to established rules.

Use Cases: Automated standardization of authority controlled metadata; transforming metadata in one schema to another schema.

A resource is being lent to another institution via interlibrary loan.  To accompany the resource, metadata is extracted in the MARC format which the borrowing library might use to load into their local system to enable lending to their user who requested the resource.

An authority record is entered in the system which includes references to the old version of the authorized heading.  When metadata is found which matches the old version, they are upgraded to the authorized version.

Reference(s):

  1. (NLA Services Framework 3.5: Generate) Make a new business object or data value through a defined algorithmic or rule-driven process. [ex. A record has an authority-controlled heading.  The heading is noted in a 4XX field of an authority record.  The rule provides for an automated change from the current heading to the authorized heading]
  2. (NLA Services Framework 3.8: Transform) Convert a business object from one form to another.  Strategies: Note that transform includes augmentation of records to support discovery at the conversion stage. Our strategy is to provide support for multiple input and output formats but with priority given to MARCXML, MODS, (MADS?), DCMI, EAD and EAC.   We have tested and decided not to map to a single internal storage format but have still not settled on exactly how data for different resource types will be stored internally. One strategy will be to build up expertise in RDF and to be actively involved in processes to map RDA data elements to the DCMI Information Model.
  3. (NLA Services Framework 3.9: Translate) Convert natural language expression from one language to an approximation in another language.
  4. (NLA Services Framework 7.2: Match) Associate a new business object being added to a registry with one or more business objects already registered that describe the same content.  Strategies: Currently we apply match and merge algorithms to incoming data to create a single merged record. Match and merge rules are similar to those we would apply to FRBRise result sets.
  5. (NLA Services Framework 7.3: Merge) Create a new business object from two or more objects in a registry that describe the same content.
  6. (NLA Services Framework 7.4: Change) Change metadata in a registry based on a set of algorithms or business rules.
  7. (e-Framework Service Genre: Generate) Make a new business object or data value through a defined algorithmic or rule-driven process.
  8. (e-Framework Service Genre: Transform) Convert a business object from one form to another form.
  9. (e-Framework Service Genre: Translate) Convert natural language expression from one natural language to another while preserving as much meaning as possible.
  10. (CollectionSpace Functional Requirements: Data Management: Metadata Configuration) Metadata Configuration: The system should include metadata configuration tools that will the user to assign metadata standards to each field in the database. The tool will allow for the incorporation of emerging and future standards.