Versions Compared

Key

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

...

Code Block
xml
xml
<didl:DIDL
    DIDLDocumentId="urn:nbn:nl:ui:10-15290" <\!-\- Identification \-->
    ...
>
    ...
</didl:DIDL>

The DIDLDocumentId attribute contains the ID of the DIDL wrapper. This CAN be the same as the OAI-Identifier that is being used to get a record. The DIDL wrapper can be used as an autonomous entity out of the OAI-PMH context, therefore a DIDL is not the same ‘thing' thing as an OAI record. There is a demand for Persistent Identifiers assigned to digital objects in the future (mandatory for the OAI-ORE project.). For libraries it is recommended to use

Code Block
urn:nbn:

...

<country code>:<isil library code>-<object id>.

Where <country code> is the ISO 3166-1 country code, <isil library code> is the ISO/NP 15511 : International Standard Identifier for Libraries and Related Organizations (ISIL)
http://www., and <object id> is a persistent database number.

Info
titleRemarks
  1. This DIDLDocumentId has in the first place a different Identifier than the OAI identifier for this record. The rationale behind this is that a DIDL document is an autonomous entity that can exist outside and separate of an OAI-record. However for easing the operational implementation, it is allowed to use the Identifier that is used for the OAI record when both, OAI record and DIDL document are inextricably bound together.
  2. {ISIL library code} ISO/NP 15511: International Standard Identifier for Libraries and Related Organizations (ISIL)http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=52666

...

  1. {object id}

...

  1. could be

...

Remarks

...

  1. the database number. It is recommended to store this number in a separate field and not to auto generate from the database id because a database update in the future will change these numbers and the persistency could be lost.

Anchor
_Toc213761485
_Toc213761485
Anchor
_Toc213761665
_Toc213761665
Anchor
_Toc214332926
_Toc214332926
Item Descriptor Elements (optional)

...

Code Block
xml
xml
<didl:DIDL ...>
  <didl:Item>
    <didl:Descriptor>...</didl:Descriptor> <\!-\- Identification \-->
    <didl:Descriptor>...</didl:Descriptor> <\!-\- Modification date \-->
    <didl:Item>...</didl:Item>
    <didl:Item>...</didl:Item>
    <didl:Item>...</didl:Item>
    ...
  </didl:Item>
</didl:DIDL>

...

Code Block
xml
xml
<didl:Item> <\!-\- Level 1 Root Item \-->
    <didl:Item> <\!-\- Level 2 Child Item \-->
      <didl:Descriptor>...</didl:Descriptor> <\!-\- Identification \-->
        <didl:Descriptor>...</didl:Descriptor> <\!-\- Modification date \-->
        <didl:Descriptor>...</didl:Descriptor> <\!-\- Object type \-->
      ...
      </didl:Item>
        <didl:Item>...</didl:Item>
        <didl:Item>...</didl:Item>
        <didl:Item>...</didl:Item>
    ...
  </didl:Item>
</didl:DIDL>

...

Code Block
xml
xml
<didl:Item>
  <didl:Item>
    <didl:Descriptor>
      <didl:Statement mimeType="application/xml">
        <dii:Identifier>urn:nbn:nl:ui:10-6748398729821</dii:Identifier>
      </didl:Statement>
    </didl:Descriptor>
    ...
  </didl:Item>
  ...
</didl:Item>
Info
titleRemarks

...

  1. For child Item elements of the root Item element accounts that this Identifier is NOT equal to the used OAI identifier or DIDL identifier
  2. The Identifier in the root Item element CAN be the same as the DIDL or OAI Identifier, but this is not recommended
  3. The namespace for dii has had to be declared in the DIDL tag
  4. The Identifier in the HAS TO BE described as an URI when applicable

Anchor
_Toc213761487
_Toc213761487
Anchor
_Toc213761667
_Toc213761667
Anchor
_Toc214332928
_Toc214332928
Descriptor Statement: Item 'modified'

...

Code Block
xml
xml
<didl:Item>
  <didl:Item>
  ...
    <didl:Descriptor>
      <didl:Statement mimeType="application/xml">
        <dcterms:modified>2006-12-20T10:29:12Z</dcterms:modified>
      </didl:Statement>
    </didl:Descriptor>
    ...
  </didl:Item>
  ...
</didl:Item>
Info
titleRemarks

...

  1. Declare the dcterms namespace in the DIDL tag
  2. The format of the date is Zulu-time; which means that it can be sorted as text
  3. There can be only one Statement element in a Descriptor element, which means that dii:identifier and dcterms:modified reside in separate Descriptor elements

Anchor
_Toc213761488
_Toc213761488
Anchor
_Toc213761668
_Toc213761668
Anchor
_Toc214332929
_Toc214332929
Descriptor Statement: Item 'ObjectType'

...

Code Block
xml
xml
<didl:Item>
  <didl:Item>
  ...
    <didl:Descriptor>
      <didl:Statement mimeType="application/xml">
        <dip:ObjectType>info:eu-repo/semantics/*descriptiveMetadata*
<descriptiveMetadata</dip:ObjectType>
      </didl:Statement>
    </didl:Descriptor>
    ...
  </didl:Item>
  ...
</didl:Item>

In the section Compound Element: representation of the complex work the representation of the complex work this ObjectType statement will be further eleborated upon.

Info
titleRemarks

...

  1. Declare the dip namespace in the DIDL tag
  2. The ObjectType in the Descriptor Statement HAS TO BE described as an URI
  3. The processing architecture we use for dissemination will be for General European repositories. The URI used is placed at the info namespace as info:eu-repo. (http://info-uri.info/) Meanwhile it is used as an un-official standard within the driver community.

Anchor
CompoundItemRepresentation
CompoundItemRepresentation
Anchor
_Toc213761489
_Toc213761489
Anchor
_Toc213761669
_Toc213761669
Anchor
_Ref214205422
_Ref214205422
Anchor
_Ref214205426
_Ref214205426
Anchor
_Toc214332930
_Toc214332930
Compound Element: representation of the complex work

...

Code Block
xml
xml
<didl:DIDL ...>
  <didl:Item>
    <didl:Item>...</didl:Item> <\!-\- metadata \-->
    <didl:Item>...</didl:Item> <\!-\- objects \-->
    <didl:Item>...</didl:Item> <\!-\- jump-off-page \-->
  </didl:Item>
</didl:DIDL>

...

Code Block
xml
xml
<didl:Item>
  <didl:Item> <\!\-- one or many occurrences -\->
    <didl:Descriptor>
      <didl:Statement mimeType="application/xml">
        <dip:ObjectType>info:eu-repo/semantics/descriptiveMetadata</dip:ObjectType>
      </didl:Statement>
    </didl:Descriptor>
  ...
</didl:Item>
<didl:Item> <\!\-- one or many occurrences -\->
  <didl <didl:Descriptor>
    <didl:Statement mimeType="application/xml">
      <dip:ObjectType>info:eu-repo/semantics/objectFile</dip:ObjectType>
    </didl:Statement>
  </didl:Descriptor>
  ...
</didl:Item>
<didl:Item> <\!-\- zero or one occurrences \-->
  <didl:Descriptor>
    <didl:Statement mimeType="application/xml">
      <dip:ObjectType>
        info:eu-repo/semantics/humanStartPage</dip:ObjectType>
      </didl:Statement>
    </didl:Descriptor>
   ...
  </didl:Item>
</didl:Item>

...

  • info:eu-repo/semantics/descriptiveMetadata (This Item occurs 1 or many times)
  • info:eu-repo/semantics/objectFile (This Item occurs 1 or many times)
  • info:eu-repo/semantics/humanStartPage (This Item occurs 0 or 1 time)
Info
titleRemarks

...

Anchor
_Toc213761490
_Toc213761490
Anchor
_Toc213761670
_Toc213761670
Anchor
_Toc214332931
_Toc214332931
ObjectType: Metadata Item

...

 

Code Block
xml
xml
<didl:Item>

 

Code Block
xml
xml
<didl:Descriptor>
  <didl:Statement mimeType="application/xml">
    <dip:ObjectType> info:eu-repo/semantics/descriptiveMetadata</dip:ObjectType>
  </didl:Statement>
</didl:Descriptor>

1

Code Block
xml
xml
<didl:Descriptor> <\!-\-  This metadata instance has its own ID number -->
  <didl:Statement mimeType="application/xml">
    <dii:Identifier>info:doi/10.1705/74836724783</dii:Identifier>
  </didl:Statement>
</didl:Descriptor>

2

Code Block
xml
xml
<didl:Descriptor> <\!-\- This record has its own Modification date -->
  <didl:Statement mimeType="application/xml">
    <dcterms:modified>2006-12-20T10:29:12Z</dcterms:modified>
  </didl:Statement>
</didl:Descriptor>

 

Code Block
xml
xml
<didl:Component>

3

Code Block
xml
xml
<didl:Resource mimeType="application/xml">
<\!-\-  the DC data -->
  <oai_dc:dc
       xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
       xmlns:dc="http://purl.org/dc/elements/1.1/"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ [http://www.openarchives.org/OAI/2.0/oai_dc.xsd]">
    <dc:creator>...</dc:creator>
    <dc:creator>...</dc:creator>
    <dc:title> ... </dc:title>
    ...
  </oai_dc:dc>
</didl:Resource>

 

Code Block
xml
xml
</didl:Component>

 

Code Block
xml
xml
</didl:Item>
Info
titleRemarks

...

  1. (Mandatory when applicable) It is recommended to identify every separate component, for future reference or re-assemble purposous. This metadata set has its own identifier, which is NOT the same as the DIDL identifier.
  2. If the date of the metadata has been changed, make sure the modification date of the root level Item is also being changed.
  3. Declare the dc namespace in the start-tag of the Resource element where you use Dublin core.

Anchor
_Toc213761491
_Toc213761491
Anchor
_Toc213761671
_Toc213761671
Anchor
_Toc214332932
_Toc214332932
ObjectType: Object Item

...

Code Block
xml
xml
<didl:Item> ... <\!-\- Below this line one can find links to one or more digital objects -->
Code Block
xml
xml
  <didl:Item> <\!-\- First Item for a File/Bitstream -->
    <didl:Descriptor>
      <didl:Statement mimeType="application/xml">
        <dip:ObjectType>info:eu-repo/semantics/objectFile</dip:ObjectType>ObjectType>
      </didl:Statement>
    </didl:Descriptor>
    ...
    <didl:Component>
       <didl:Resource mimeType="application/pdf" ref="http://my.server.nl/report.pdf"/><>
    </didl:Component>
  </didl:Item>
Code Block
xml
xml
  <didl:Item> <\!-\- Second Item for a File/Bitstream -->
    <didl:Descriptor>
      <didl:Statement mimeType="application/xml">
        <dip:ObjectType>info:eu-repo/semantics/objectFile</dip:ObjectType>
      </didl:Statement>
    </didl:Descriptor>
    ....
    <didl:Component>
      <didl:Resource mimeType="application/pdf" ref="http://my.server.nl/appendix.pdf"/><didl>
    <didl:Component>
  </didl:Item>
Code Block
xml
xml
  <didl:Item> <\!-\- Third Item for a File/Bitstream -->
    <didl:Descriptor>
      <didl:Statement mimeType="application/xml">
        <dip:ObjectType>info:eu-repo/semantics/objectFile</dip:ObjectType>
      </didl:Statement>
    </didl:Descriptor>
    ...
    <didl:Component>
      <didl:Resource mimeType="application/pdf" ref="http://my.server.nl/datasheets.xls"/><didlxls"/>
    <didl:Component>
  </didl:Item>
Code Block
xml
xml
</didl:Item>

As you can see in the above example, the Resource locations do not appear in several components within one Item, but each Resource location is wrapped in an Item element. The rationale behind this is that each Bit stream of file can have its own Identifier. On the three dots "..." (given in the examples) one may place the Identifier and modified tags, which is similar to the metadata Item.

Info
titleRemarks

...

  1. The order of the object components should be in a logical reading order! The Item with chapter 1 should be followed by the next sibling Item element that contains chapter 2, etc... This way the service provider can make a better presentation. Making the order explicit by placing sequence numbers is being specified in the next version of the specification.
  2. If there are important modification dates for the Resource element, propagate these date changes upwards though out the parent Item elements that encapsulate the modified child Item element.
  3. Only add Identifiers when there actually are any
  4. If there are no Identifiers for the ObjectType Item elements, the Identifier of the DIDL element will be used by the service provider.
  5. Use for a modified or Identifier element a separate <Descriptor> <Statement> element construction
  6. The rule of thumb is that if a Bitstream or file has its own identifier, the wrapper is an Item element. To keep the possibility open for a Bitstream to have an Identifier, we use the Item element as default to wrap a resource location.

Anchor
_Toc213761492
_Toc213761492
Anchor
_Toc213761672
_Toc213761672
Anchor
_Toc214332933
_Toc214332933
ObjectType: Jump-off-page Item

...

Code Block
xml
xml
<didl:Item> ... <\!-\- Below this line; an Item with a link to one optional Intermediate page -->
Code Block
xml
xml
  <didl:Item>
    <didl:Descriptor>
      <didl:Statement mimeType="application/xml">
        <dip:ObjectType> info:eu-repo/semantics/humanStartPage </dip:ObjectType>
      </didl:Statement>
    </didl:Descriptor>
    ...
    <didl:Component>
      <didl:Resource mimeType="application/html" ref="http://my.server.nl/mypub.html"/><>
    </didl:Component>
  </didl:Item>
Code Block
xml
xml
</didl:Item>