Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Note

Work in Progress

Expand
titleClick here to show Table of Contents...

Table of Contents

Abstract

...

Info

This form field is only available in the metadata input form for assets ingested with content types Book, Publication, Publication issue.

...

Excerpt

Status
colourRed
titleAutogenerated

MODS Element name: <originInfo><dateCreated> <originInfo><dateCreated keyDate="yes"> (Creation date) or <originInfo><dateIssued> <originInfo><dateIssued keyDate="yes"> (Issuance date); <originInfo><copyrightDate> (Copyright date)

Short definition:  Information about the original creation, publication or copyright date of the resource (adapted from MODS standard). An asset's metadata need to contain either a Creation date or an Issuance date. If both dates are present, the asset cannot be published to the Collections portal.

Input guidelines: It is strongly recommended to input known dates in a structured format: YYYY-MM-DD (year-month-date). You can also enter year and month (YYYY-MM), or year only (YYYY). For unknown dates, enter "undated". For uncertain dates, select a date qualifier (approximate, inferred, or questionable). Alternatively, a limited number of textual date information can be entered: circa/ca/c/ca./c. YYYY, 19th century, 1960s, late 1850s, mid 4th century.

Creation Date: Original creation date of the resource, most relevant to discovery of the resource by end-users. Input the original Creation date/ Start date of creation of the resource. End date of creation is recommended if a date range is applicable, but it is not mandatory.

Issuance Date: The date that the resource was published, released, or issued. End date of issuance is recommended if a date range is applicable, but it is not mandatory.

Copyright Date: A date in which a resource is copyrighted (date copyright was established, e. g. through registration).

Definition

Information about the original creation, publication or copyright date of the resource (adapted from MODS standard). Can be single date (point) or date range. An asset's metadata need to contain either a Creation date or an Issuance date. If both dates are present, the asset cannot be published to the Collections portal.

The following types of date can be used for the DAMS:

  • Creation Date: Original creation date of the resource, most relevant to discovery of the resource by end-users. Input the original Creation date/ Start date of creation of the resource. End date of creation is recommended if a date range is applicable, but it is not mandatory.
  • Issuance Date: The date that the resource was published, released, or issued. End date of issuance is recommended if a date range is applicable, but it is not mandatory.
  • Copyright Date: A date in which a resource is copyrighted (date copyright was established, e. g. through registration).

DAMS input form fields

Date

...

radio button option selection

  • Date created
  • Date issued

...

dateCreated[@keyDate]
(attribute of dateCreated)

dateIssued[@keyDate]
(attribute of dateIssued)

...

Info

This selection is only available in the metadata input form for assets ingested with content types Book, Publication, Publication issue.

Multiexcerpt include
MultiExcerptNameDate-keyDate

...

dateCreated[@point="start"]

...

Multiexcerpt include
MultiExcerptNameDate-dateCreated

...

dropdown selection

  • (empty/none)
  • approximate
  • inferred
  • questionable

...

Note

It is strongly recommended to input uncertain dates in a structured format as well and indicate the level of certainty by selecting one of the date qualifiers.

Warning

Do not input dates containing a question mark in the DAMS input form.

Multiexcerpt include
MultiExcerptNameDate-qualifier

...

see Date Created/ Date Created Start

...

dropdown selection

  • (empty/none)
  • approximate
  • inferred
  • questionable

...

see Start Date Qualifier (Creation date)

...

Info

This form field is only available in the metadata input form for assets ingested with content types Book, Publication, Publication issue.

see Date Created/ Date Created Start

...

dropdown selection

  • (empty/none)
  • approximate
  • inferred
  • questionable

...

Info

This form field is only available in the metadata input form for assets ingested with content types Book, Publication, Publication issue.

see Start Date Qualifier (Creation Date)

...

Info

This form field is only available in the metadata input form for assets ingested with content types Book, Publication, Publication issue.

see Date Created End

...

dropdown selection

  • (empty/none)
  • approximate
  • inferred
  • questionable

...

Info

This form field is only available in the metadata input form for assets ingested with content types Book, Publication, Publication issue.

see End Date Qualifier (Creation Date)

System-generated, machine-readable date value derived from either Creation Date or Issuance Date.

Input guidelines: The system will create a machine-readable date element with a keyDate attribute based on the user-provided information for Date created or Date issued. If a date range is specified, only the start date will be used as key date. If textual date information is provided, the key date will be a numerical date approximating the textual date information. The machine-readable date is for instance used for sorting of search results.

Note

The ingest process currently ignores a keyDate attribute set by users when preparing metadata as MODS XML. Instead, the system will create a new machine-readable date element with a keyDate attribute based on dateIssued or dateCreated (in this order and depending on which of the two is available). Any user-provided keyDate attribute will be stripped from the metadata upon ingest.

If you want to designate a specific date element as the key date in metadata prepared for batch ingest, add the following attribute-value pair to the respective element: keyGen="yes".

Definition

System-generated, machine-readable date value derived from either Creation Date or Issuance Date.

DAMS input form fields


System-generated metadata element. These elements cannot be edited in the DAMS metadata web form.

MODS Element description

Element <originInfo>

http://www.loc.gov/standards/mods/userguide/origininfo.html

Guidelines for use

<originInfo> is a container element that contains all subelements related to publication and origination information. It includes all dates associated with the creation, issuance, and/or publication of the resource. Dates associated with the temporal content of the resource go under <subject>, and dates associated with the metadata go in <recordInfo>. Data is input only within each subelement.

Attributes

Currently no attributes for originInfo are implemented in the DAMS.

Subelements

The following subelements of <originInfo> are used in the DAMS:

  • dateCreated
  • dateIssued
  • (copyrightDate)
  • (place)
  • (publisher)

Subelement <originInfo><dateCreated>

Guidelines for use

...

MultiExcerptNameDate-dateCreated

...

An asset's metadata need to contain either a Creation date or an Issuance date. If both dates are present, the asset cannot be published to the Collections portal.

...

Alternatively, a limited number of textual date information can be entered:

  • 16th century
  • sixteenth century
  • 1960s
  • early 1960s
  • mid 1960s
  • late 1960s
  • early 16th century
  • mid sixteenth century
  • late 16th century
  • first half of 16th century
  • second half of sixteenth century
  • first quarter of 13th century
  • second quarter of 13th century
  • third quarter of thirteenth century
  • fourth quarter of 13th century
  • circa/ca/c/ca./c. YYYY

The DAMS will create a machine-readable date element with a keyDate attribute that approximates the textual date information. The machine-readable date is for instance used for sorting of search results.

<dateCreated> is repeatable to accommodate start and end points and auto-generated, machine-readable, w3cdtf encoded, keyDate version of <dateCreated>.

Attributes

...

values:

  • start
  • end

The

...

values:

  • yes

...

MultiExcerptNameDate-keyDate

...

system will create a

...

machine-readable date element with a keyDate attribute based on the user-provided information for Date created or Date issued. If a date range is specified, only the start date will be used as key date. If textual date information is provided, the key date will be a numerical date approximating the textual date information. The machine-readable date is for instance used for sorting of search results.

Note

The ingest process currently ignores a keyDate attribute set by users when preparing metadata as MODS XML. Instead, the system will create a new machine-readable date element with a keyDate attribute based on dateIssued or dateCreated (in this order and depending on which of the two is available). Any user-provided keyDate attribute will be stripped from the metadata upon ingest.

If you want to designate a specific date element as the key date in metadata prepared for batch ingest, add the following attribute-value pair to the respective element: keyGen="yes".

Attributes

Attribute nameDetailsXPath syntax examples
point

value:

  • start
originInfo/dateCreated[@keyDate="yes" and @point="start"]
qualifierkeyDate

valuesvalue:

  • approximate
  • inferrred
  • questionableyes

Specify a qualifier (approximate, inferred, or questionable) for uncertain dates:

  • approximate: characterizes a date that may not be exact, but is approximated, or is a rough estimate. Examples in other catalogs or finding aids might be “ca. 1972” or “circa 1972”.
  • inferred: characterizes a date that has been deduced by looking at evidence found on the resource or from outside of the resource. For example, if a resource contains a bibliography that includes books published in 1852, one may deduce that the date of the resource is “not before 1852”. Another example, if a resource says that it was written during the American Civil War, one may deduce that the date of the resource is “between 1861 and 1865”. Inferred dates can also be a simple, single date, for example “1915” if it was deduced that 1915 must be the date.
  • questionable characterizes a date that is probable, but might be wrong. Examples in other catalogs or finding aids might be “1972?” or ""?1972", however do not enter dates containing a question mark in DAMS form fields
    Multiexcerpt
    MultiExcerptNameDate-qualifier
    keyDate

    The system will create a new machine-readable date element with a keyDate attribute based on the user-provided information for Date created or Date issued. If a date range is specified, only the start date will be used as key date.

    originInfo/dateCreated[@qualifier@keyDate="approximateyes"]
    encoding

    valuesvalue:

    • w3cdtf

    Used on automatically generated date element only.

    originInfo/dateCreated[@keyDate="yes" and @encoding="w3cdtf"]

    Subelements

    No subelements for dateCreated.

    Subelement <originInfo><dateIssued>

    Guidelines for use

    Multiexcerpt include
    MultiExcerptNameDate-dateCreated

    Attributes

    ...

    values:

    • start
    • end

    The 'start' date value is used for the first date of a range, or for a single date, if an end date is not present.

    ...

    values:

    • yes

    Multiexcerpt include
    MultiExcerptNameDate-keyDate

    ...

    The system will create a machine-readable date element with a keyDate attribute based on the user-provided information for Date created or Date issued. If a date range is specified, only the start date will be used as key date. If textual date information is provided, the key date will be a numerical date approximating the textual date information. The machine-readable date is for instance used for sorting of search results.

    Note

    The ingest process currently ignores a keyDate attribute set by users when preparing metadata as MODS XML. Instead, the system will create a new machine-readable date element with a keyDate attribute based on dateIssued or dateCreated (in this order and depending on which of the two is available). Any user-provided keyDate attribute will be stripped from the metadata upon ingest.

    If you want to designate a specific date element as the key date in metadata prepared for batch ingest, add the following attribute-value pair to the respective element: keyGen="yes".

    Attributes

    Attribute nameDetailsXPath syntax examples
    point

    value:

    • start
    originInfo/dateIssued[@keyDate="yes" and @point="start"]
    qualifierkeyDate

    valuesvalue:

    • approximate
    • inferrredyes
    • questionable

    Multiexcerpt include
    MultiExcerptNameDate-qualifierkeyDate
    PageWithExcerptKey Date (autogenerated)

    originInfo/dateIssued[@qualifier@keyDate="inferredyes"]
    encoding

    valuesvalue:

    • w3cdtf
    Used on automatically generated date element only.
    originInfo/dateIssued[dateCreated[@keyDate="yes" and @encoding="w3cdtf"]

    Subelements

    No subelements for dateIssued.

    Subelement <originInfo><copyrightDate>

    Status
    colourBlue
    titleRepeatable

    Guidelines for use

    Input known dates in a structured format: YYYY-MM-DD (year-month-date). You can also enter year and month (YYYY-MM), or year only (YYYY).

    Attributes

    Currently no attributes for originInfo are implemented in the DAMS.

    Subelements

    No subelements for copyrightDate.

    XML Examples

    Code Block
    languagexml
    collapsetrue
    <!-- YYYY-MM-DD entry -->
    <originInfo>
    	<dateCreated point="start">1972-10-25</dateCreated>
    	<dateCreated point="start" encoding="w3cdtf" keyDate="yes">1972-10-25</dateCreated> </originInfo>
    
    <!-- YYYY-MM-DD to YYYY-MM-DD range entry -->
    <originInfo>
    	<dateCreated point="start">2016-01-01</dateCreated>
    	<dateCreated point="end">2017-05-10</dateCreated>
    <dateCreated point="start" encoding="w3cdtf" keyDate="yes">2016-01-01</dateCreated> </originInfo>
    
    <!-- questionable YYYY entry -->
    <originInfo>
    	<dateCreated point="start" qualifier="questionable">1894</dateCreated>
    	<dateCreated point="start" qualifier="questionable" encoding="w3cdtf" keyDate="yes">1894>2001-01-01</dateCreated>
    </originInfo>
    
    <!-- inferred YYYY entry -->
    <originInfo>
    	<dateCreated point="start" qualifier="inferred">1916</dateCreated>
    	<dateCreated point="start" qualifier="inferred" encoding="w3cdtf" keyDate="yes">1916-01-01</dateCreated>
    </originInfo>
    
    <!-- approximate partial decade entry -->
    <originInfo>
    	<dateCreated point="start" qualifier="approximate">late 1990s</dateCreated>
    	<dateCreated point="start" qualifier="approximate" encoding="w3cdtf" keyDate="yes">1997-01-01</dateCreated>
    </originInfo>
    
    <!-- undated entry -->
    <originInfo>
    	<dateCreated keyDate="yes">undated</dateCreated>
    </originInfo>
    
    <!-- approximate century entry -->
    <originInfo>
    	<dateCreated point="start" qualifier="approximate">circa 9th century</dateCreated>
    	<dateCreated point="start" qualifier="approximate" encoding="w3cdtf" keyDate="yes">0800-01-01</dateCreated>
    </originInfo>

    Mappings

    Dublin Core

    Depending on the direction of mapping necessary, check

    ...

    dateIssued[point="end"]
    Dublin Core fieldMapping conditionMODS elementNotes
    dc:dateMODS to DCdateCreated[point@keyDate="startyes"]The date value in the MODS element is prefixed with the text "Created: ".
    dc:datedateCreated[point="end"]Creation start and end date are concatenated, separated by "/". The resulting string is prefixed with the text "Created: ".dc:datedateIssued[point="startMODS to DCdateIssued[@keyDate="yes"]The date value in the MODS element is prefixed with the text "Issued: ".dc:dateCreation start and end date are concatenated, separated by "/". The resulting string is prefixed with the text "Issued: ".N/AcopyrightDateCurrently, there is no mapping of copyrightDate to DC implemented in the DAMS.

    MARC 21

    see http://www.loc.gov/standards/mods/mods-mapping.html#publication. The following specific guidelines apply for the DAMS:

    MARC 21 fieldMapping conditionMODS elementNotes
    *MARC to MODS*[@encoding]Only use encodingdateCreated[@keyDate="w3cdtf" or do not use the encoding attribute at all.260$gdateCreatedThe MODS field dateOther is not implemented in the DAMS. Map MARC field 260$g to dateCreated instead.
    264$cMARC indicator 2 has values 0, 3dateCreatedThe MODS field dateOther is not implemented in the DAMS. Map MARC field 264$c to dateCreated instead.

    264$c

    MARC indicator 2 has value 2dateIssuedThe MODS field dateOther is not implemented in the DAMS. Map MARC field 264$c to dateIssued instead.
    033note[@type="date captured"]The MODS field dateCaptured is not implemented in the DAMS. Map MARC field 033 to a note element with type "date captured" instead.

    046$m

    N/AThe MODS field dateValid is not implemented in the DAMS.046$nN/AThe MODS field dateValid is not implemented in the DAMS.046$jN/AThe MODS field dateModified is not implemented in the DAMS.534$cdateCreated/ dateIssued

    MARC field 534 describes an original version, i.e. likely a different Expression/ Manifestation than what is described by the main bibliographic fields in the same record. Consider using a MARC record describing the same Expression/ Manifestation of a work that is digitized and ingested in the DAMS.

    Check textual statement in MARC subfield 534$c carefully to determine whether to map to dateCreated or dateIssued.

    775$ddateCreated/ dateIssued

    MARC field 775 describes another available edition, i.e. likely a different Expression/ Manifestation than what is described by the main bibliographic fields in the same record. Consider using a MARC record describing the same Expression/ Manifestation of a work that is digitized and ingested in the DAMS.

    Check textual statement in MARC subfield 775$d carefully to determine whether to map to dateCreated or dateIssued.

    776$ddateCreated/ dateIssued

    MARC field 776 describes another available physical form, i.e. likely a different Manifestation than what is described by the main bibliographic fields in the same record. Consider using a MARC record describing the same Manifestation of a work that is digitized and ingested in the DAMS.

    Check textual statement in MARC subfield 776$d carefully to determine whether to map to dateCreated or dateIssued.

    yes"]Do not map MARC data into MODS element with attribute keyDate.
    *MARC to MODSdateIssued[@keyDate="yes"]Do not map MARC data into MODS element with attribute keyDate.

    Solr

    In general, all MODS metadata is imported into the DAMS Solr server upon ingest. The ingest process generates Solr fields typically named according to the following schema:

    ...

    dateCreated[point="start"]
    DAMS metadata elementMapping conditionSolr DAMSSolr Collections portalNotes[not(@keyDate="yes")]mods_dateCreated_startdate_created_issued
    Multiexcerpt
    MultiExcerptNamesolr-date-created-issued

    date_created_issued is generated during the publication process. The field contains the date information in the MODS metadata, as entered by the metadata contributor.

    date_created_issued is used to display date information in the list of search results in the Collections portal and on the full metadata (landing page) view in the Collections portal. The list of search results can be sorted by mods_keyDate_sort.

    dateCreated[point="end"]mods_dateCreated_endN/ACreation end date is not displayed in the Collections portal.
    dateIssued[point="start"][not(@keyDate="yes")]mods_dateIssued_startdate_created_issued

    Multiexcerpt include
    MultiExcerptNamesolr-date-created-issued

    dateIssued[point="end"]mods_dateIssued_endN/AIssuance end date is not displayed in the Collections portal.*[@keyDate="yes"]
    mods_keyDate_sortdisplay_date

    mods_keyDate_sort is generated during ingest from the date value marked as key date in the MODS metadata.mods_keyDate_sort is used for sorting the list of search results in the Collections portal.

    display_date is generated during the publication process. The field contains the first 4 characters of the date value marked as key date in the MODS metadata.

    display_date is used to generate the search facets for Date Created/Date Issued and Public Domain Status in the Collections portal.

    dc:datedc.dateN/ACf. MODS to Dublin Core metadata mapping. Separate dc.date Solr fields are generated for Creation/Issuance date(s) as entered by the metadata provider and for the key date*[@keyDate="yes"]
    mods_keyDate_sortmods_keyDate_sort

    mods_keyDate_sort is generated during ingest from the date value marked as key date in the MODS metadata.

    mods_keyDate_sort is used for sorting the list of search results in the Collections portal.