OpenWMS Metadata Guide

Source Metadata


Section: Provenance Event

Last updated: April 24th, 2009
Name
provenanceEvent
Schema
rulib
Definition
A parent element for all elements comprising the Provenance Event. The Provenance Event elements, taken together, describe any action occurring in a particular place and time that pertains to the origin and history of successive ownership or custodianship, such as creation, acquisition, exchange, deaccession, etc. The Provenance Event subelements include:
ID
Type [of event]
Label [event name]
Place
Date & Time
Detail [note]
Associated Entity
   Identifier
   Name
   Role
   Affiliation
   Reference
   Detail
Associated Object
   Identifier
   Type [of object]
   Relationship
   Name
   Reference [URL or other locator]
   Detail [note]
Usage Note
Use the Provenance Event elements to track the provenance of a resource, and/or when you wish to link the bibliographic record (the description of the resource) to supporting documentation of provenance (e.g., an accession record or digitized custody record, such as a deed of gift) or information about an agent (e.g., donor) related to the provenance. The Provenance Event elements allow you to bring together in one place all the information about the resource's origin and history of successive ownership or custodianship. When there are multiple events of a single type, input each as a separate event.
Repeatable
Y
Name
provenanceEventID
Label
not applicable; system-supplied; does not appear on form
Schema
rulib
Definition
A system-assigned unique character string that identifies this particular event and distinguishes it from others. The provenanceEventID is comprised of a value (the unique character string) and an authority attribute, which indicates the authoritative source for the identifier. (The authority attribute is supplied by the system and does not appear on the form.)
Controlled Vocabulary
provenance event 001, provenance event 002, etc. [source: rulib]
Repeatable
N
Name
provenanceEventIDAuthority
Label
not applicable; does not appear on form
Schema
local
Definition
The authoritative source for the Provenance Event ID.
Usage Note
The provenanceEventIDAuthority is an attribute of the Provenance Event ID; it is supplied by the system and does not appear on the form.
Controlled Vocabulary
rulib [source: rulib]
Repeatable
N
Name
provenanceEventType
Label
Provenance Event - Type
Schema
rulib
Definition
The kind of provenance event in the resource's lifecycle, such as acquisition.
Controlled Vocabulary
Acquisition; Appraisal; Audit; Capture; Creation; Deaccession; Deposit; Donation; Exchange; Gift; Inventory; Issue (publication, broadcast, or release); Loan; Missing; Origination; Processing; Purchase; Transfer of Ownership; Other [source: rulib]
Repeatable
N
Name
provenanceEventLabel
Label
Provenance Event - Label
Schema
rulib
Definition
A specific name for an event in the resource's lifecycle, supplied by the cataloger to provide more meaningful displays. Allows the organization to use its own local terminology in labeling an event. Labels should be succinct and descriptive.
Usage Note
Optional within the element.
Example(s)
2009 Annual weeding
Repeatable
N
Name
provenanceEventPlace
Label
Provenance Event - Place
Schema
rulib
Definition
The location where the specified event occurred. Can include building, address, city, state, country. Free-text, although the organization can choose to support country codes, TGN, etc.
Example(s)
Flemington (N.J.)
Brazil
Library of Congress Madison Building, Washington, D.C.
Repeatable
N
Name
provenanceEventDateTime
Label
Provenance Event - Date & Time
Schema
rulib
Definition
The date (year, month, date) and/or time (in timecode format) when the specified event occurred.
Format
Formatting is ISO 8601-W3C, i.e.:
YYYY-MM-DD or YYYY-MM-DDThh:mm:ssTZD

Use the components as indicated below, with exactly this punctuation. Note that the "T" appears literally in the string, to indicate the beginning of the time element, as specified in ISO 8601.
Year:
   YYYY (e.g., 1997)
Year and month:
   YYYY-MM (e.g., 1997-07)
Complete date:
   YYYY-MM-DD (e.g., 1997-07-16)
Complete date plus hours and minutes:
   YYYY-MM-DDThh:mmTZD (e.g., 1997-07-16T19:20+01:00)
Complete date plus hours, minutes and seconds:
   YYYY-MM-DDThh:mm:ssTZD (e.g., 1997-07-16T19:20:30+01:00)
Complete date plus hours, minutes, seconds and a decimal fraction of a second:
   YYYY-MM-DDThh:mm:ss.sTZD (e.g., 1997-07-16T19:20:30.45+01:00)

where:
   YYYY = four-digit year
   MM = two-digit month (01=January, etc.)
   DD = two-digit day of month (01 through 31)
   hh = two digits of hour (00 through 23) (am/pm NOT allowed)
   mm = two digits of minute (00 through 59)
   ss = two digits of second (00 through 59)
   s = one or more digits representing a decimal fraction of a second
   TZD = time zone designator (Z or +hh:mm or -hh:mm)

Time zone offsets may be handled in either of two ways:
1. Times are expressed in local time, together with a time zone offset in hours and minutes. A time zone offset of "+hh:mm" indicates that the date/time uses a local time zone which is "hh" hours and "mm" minutes ahead of UTC (Coordinated Universal Time). A time zone offset of "-hh:mm" indicates that the date/time uses a local time zone which is "hh" hours and "mm" minutes behind UTC.
2. Times are expressed in UTC, with a special UTC designator ("Z").
Example(s)
1994-11-05T08:15:30-05:00 [method 1]
[corresponds to November 5, 1994, 8:15:30 am, US Eastern Standard Time]
1994-11-05T13:15:30Z [method 2]
[corresponds to the same instant]
Repeatable
N
Name
provenanceEventDetail
Label
Provenance Event - Detail
Schema
rulib
Definition
A free-text explanatory note about or describing the provenance event, such as circumstances surrounding an acquisition.
Example(s)
Acquired through the FIAF Reel Emergency Project.
Repeatable
N
Name
provenanceEventAssociatedEntity
Group Label
Provenance Event - Associated Entity
Schema
rulib
Definition
The Associated Entity subelement under Provenance Event is a parent element for all elements pertaining to an entity (person, corporate body, or conference) associated with the provenance event. For example, a donor might be the agent associated with an acquisition event. The Associated Entity subelements of a Provenance Event include:
Identifier
Name
Role
Affiliation
Reference
Detail
Usage Note
Use the Associated Entity elements when you wish to link the bibliographic record (the description of the resource) to information about agents associated with the provenance of the resource. Linking information about associated agents (and related objects; see below) allows you to bring together in one place all the information about a resource's provenance.
Repeatable
Y
Name
provenanceEventAssociatedEntityIdentifier
Label
Provenance Event - Associated Entity - Identifier
Schema
rulib
Definition
A unique character string that identifies this particular associated entity and distinguishes it from others. The provenanceEventAssociatedEntityIdentifier is comprised of a value (the unique character string) and two attributes: type and authority.
Usage Note
Use the identifier assigned by the name authority, if there is one. Otherwise, the number is system supplied.
Example(s)
500045890
nr 98021052
Repeatable
N
Name
provenanceEventAssociatedEntityIdentifierType
Label
Provenance Event - Associated Entity - Identifier Type
Schema
rulib
Definition
The kind of identifier assigned to the Provenance Event Associated Entity (global or local). A global identifier will reference an authority or biographical record intended to globally identify the agent, such as the LC Name Authority File record or a ULAN record maintained by the Getty.
Controlled Vocabulary
global; local [source: rulib]
Repeatable
N
Name
provenanceEventAssociatedEntityName
Label
Provenance Event - Associated Entity - Name
Schema
rulib
Definition
The name of a person, corporate body, or conference associated with the provenance event.
Usage Note
Use the authoritative version of name, as found in an authority file, if possible, e.g. Agnew, Grace or Hunter Museum.
Format
In general, personal names are entered in inverted order, e.g., Agnew, Grace, whereas corporate names are entered in direct order, e.g., Buddy Holly Center. If possible, use the name as established in a national or international authority file, such as Library of Congress Authorities. When establishing a name for the first time, if possible formulate the name according to an established content standard such as the Anglo-American Cataloging Rules (AACR2).
Example(s)
Einstein, Daniel, 1951-
Ringling Museum of the Circus
Repeatable
N
Name
provenanceEventAssociatedEntityRole
Label
Provenance Event - Associated Entity - Role
Schema
rulib
Definition
The function performed by the agent, relative to the particular event; indicates the relationship between the agent and the event. For example, the role of a person associated with a 'donation' event would likely be 'donor.'
Usage Note
Choose the single most specific role appropriate for the event type. For example, for a donation event, choose the role of 'donor' for the person donating the material, even if that person performs other roles in other events or contexts. If an agent plays more than one role in the event, select the most prominent or important role and document the other role(s) in the associatedEntityDetail element (below).
Controlled Vocabulary
Actor; Adapter; Author of afterword, colophon, etc.; Annotator; Bibliographic antecedent; Applicant; Author in quotations or text abstracts; Architect; Arranger; Artist; Assignee; Associated name; Attributed name; Auctioneer; Author of dialog; Author of introduction; Author of screenplay; Author; Binding designer; Bookjacket designer; Book designer; Book producer; Binder; Bookplate designer; Bookseller; Conceptor; Choreographer; Collaborator; Client; Calligrapher; Collotyper; Commentator; Composer; Compositor; Conductor; Censor; Contestant-appellee; Collector; Compiler; Contestant; Contestant-appellant; Copyright claimant; Complainant-appellee; Copyright holder; Complainant; Complainant-appellant; Creator; Correspondent; Corrector; Consultant; Consultant to a project; Costume designer; Contributor; Contestee-appellee; Cartographer; Contractor; Contestee; Contestee-appellant; Curator; Commentator for written text; Defendant; Defendant-appellee; Defendant-appellant; Degree grantor; Dissertant; Delineator; Dancer; Donor; Depositor; Draftsman; Director; Designer; Distributor; Dedicatee; Dedicator; Dubious author; Editor; Engraver; Electrotyper; Engineer; Etcher; Expert; Facsimilist; Film editor; Former owner; Funder; Forger; Graphic technician; Honoree; Host; Illustrator; Illuminator; Inscriber; Inventor; Instrumentalist; Interviewee; Interviewer; Librettist; Libelee-appellee; Libelee; Lender; Libelee-appellant; Libelant-appellee; Libelant; Libelant-appellant; Landscape architect; Licensee; Licensor; Lithographer; Lyricist; Metadata contact; Moderator; Monitor; Metal-engraver; Musician; Narrator; Opponent; Originator; Organizer of meeting; Other; Owner; Patron; Publishing director; Publisher; Proofreader; Photographer; Platemaker; Printer of plates; Papermaker; Process contact; Production personnel; Performer; Programmer; Producer; Printer; Patent applicant; Plaintiff-appellee; Plaintiff; Patent holder; Plaintiff-appellant; Rubricator; Recording engineer; Recipient; Redactor; Renderer; Researcher; Reviewer; Respondent-appellee; Respondent; Respondent-appellant; Research team head; Research team member; Scientific advisor; Scenarist; Scribe; Sculptor; Secretary; Signer; Singer; Speaker; Sponsor; Surveyor; Standards body; Stereotyper; Thesis advisor; Transcriber; Translator; Type designer; Typographer; Vocalist; Writer of accompanying material; Woodcutter; Wood-engraver; Witness [source: MARC Code Lists-Relators]
Repeatable
N
Name
provenanceEventAssociatedEntityAffiliation
Label
Provenance Event - Associated Entity - Affiliation
Schema
rulib
Definition
The name of an organization with which the agent is associated. Affiliation refers to a corporate body with whom an entity is professionally or formally affiliated at the time of the event.
Usage Note
Use only when the affiliation is relevant to the event or used to provide identification or authority to the related agent. Select the most specific term appropriate for the event type.
Format
In general, enter the name in direct order, e.g., Buddy Holly Center. If possible, use the name as established in a national or international authority file, such as Library of Congress Authorities. When establishing a name for the first time, if possible formulate the name according to an established content standard such as the Anglo-American Cataloging Rules (AACR2).
Example(s)
Martin and Osa Johnson Safari Museum
Repeatable
N
Name
provenanceEventAssociatedEntityReference
Label
Provenance Event - Associated Entity - Reference
Schema
rulib
Definition
URL or other locator for information about the agent. May be a reference to an authority record, organization website, biographical record or other record associated with identifying and documenting the entity.
Example(s)
http://www.buddyhollycenter.org/
Repeatable
N
Name
provenanceEventAssociatedEntityDetail
Label
Provenance Event - Associated Entity - Detail
Schema
rulib
Definition
A free-text explanatory note about or describing the associated agent, often a description of the agent's role and association within the event.
Example(s)
The original owner of the collection.
Repeatable
N
Name
provenanceEventAssociatedObject
Group Label
Provenance Event - Associated Object
Schema
rulib
Definition
A parent element for all elements pertaining to an object associated with the provenance event. Usually the object will be a document. For example, the deed of gift might be an object associated with an acquisition event. The Associated Object subelements of a Provenance Event include:
Identifier
Type
Relationship
Name
Reference
Detail
Usage Note
Use the Associated Object elements when you wish to link the bibliographic record (the description of the resource) to supporting documentation. This document may be a digital supporting document, such as a purchase catalog or deed of gift, or other associated resource, such as resource acquired at the same time from the same entity. This reference documents associations related to provenance that may not be relevant to those who ultimately discover and use the resource for its information. Linking associated documents (and related agents; see above) allows you to bring together in one place all the information about a resource's provenance.
Repeatable
Y
Name
provenanceEventAssociatedObjectIdentifier
Label
Provenance Event - Associated Object - Identifier
Schema
rulib
Definition
A unique character string that identifies this particular associated object and distinguishes it from others. The provenanceEventAssociatedObjectIdentifier is comprised of a value (the unique character string) and two attributes: type and authority.
Usage Note
Use the identifier assigned by the object repository or an authoritative number that is globally assigned, such as an ISBN. Otherwise, the number is system supplied.
Example(s)
0765575139
Repeatable
N
Name
provenanceEventAssociatedObjectIdentifierType
Label
Provenance Event - Associated Object - Identifier Type
Schema
rulib
Definition
The kind of identifier assigned to the Provenance Event Associated Object (global or local). A global identifier will generally be assigned and maintained by an agency tasked with maintaining a global registry. Examples include ISBN and DOI.
Controlled Vocabulary
global; local [source: rulib]
Repeatable
N
Name
provenanceEventAssociatedObjectType
Label
Provenance Event - Associated Object - Type
Schema
rulib
Definition
The kind of object associated with the provenance event.
Controlled Vocabulary
Catalog; Correspondence; Deed of gift; Document; Invoice; Other; Policy; Procedure; Report; Research; Resource [source: rulib]
Repeatable
N
Name
provenanceEventAssociatedObjectRelationship
Label
Provenance Event - Associated Object - Relationship
Schema
rulib
Definition
Documents the relationship of the associated object to the event. Similar in purpose to the "role" subelement for Associated Entity.
Controlled Vocabulary
Documents; Has documentation; Is part of; Has part; Is format of; Has format; Is referenced by; References; Is basis for; Is based on; Requires; Other
Repeatable
N
Name
provenanceEventAssociatedObjectName
Label
Provenance Event - Associated Object - Name
Schema
rulib
Definition
Any name or title you wish to assign to the associated object in order to clearly identify it to staff and end users. Where applicable, use the main or authoritative ("uniform") title you would assign if you were cataloging the object in its own right. When creating a name, be succinct and descriptive.
Example(s)
Purchase Catalog, Jane Doe collection
Gift inventory, John Smith donation
Repeatable
N
Name
provenanceEventAssociatedObjectReference
Label
Provenance Event - Associated Object - Reference
Schema
rulib
Definition
URL or other locator for information about the object. The associatedObjectReference is comprised of a value and a type attribute.
Example(s)
http://www.myarchive.org/press_releases/20081112
Repeatable
N
Name
provenanceEventAssociatedObjectReferenceType
Label
Provenance Event - Associated Object - Reference Type
Schema
rulib
Definition
The type of reference (physical or digital). This may be a URL that links to a digital representation of the object or a locator (such as a shelving locator) to a physical object. This may also be a resolvable reference to a metadata surrogate for the associated object.
Controlled Vocabulary
physical; digital
Repeatable
N
Name
provenanceEventAssociatedObjectDetail
Label
Provenance Event - Associated Object - Detail
Schema
rulib
Definition
A free-text explanatory note about or describing the associated object, usually describing the role and/or association of the associated object within the event.
Example(s)
Correspondence was initiated by curator Jane Doe and continued by her successor after January 1, 2006.
Repeatable
N




 
Menu
Overview
Download
Help Guides
User Manual
Installation Guide
Metadata Guide
File Policy and Uploading Guide
Support
Known Bugs
Report a Bug
Feature Requests
Rutgers Support Request
Contact
Submit a Comment
Attribution/Copyright
Version 7.3.1
Rutgers University Libraries - Copyright ©2014