Graphical view:

Related discussions:

pbcoreresources.org
Browse: Home / v2 / Elements / pbcoreDescriptionDocument / pbcoreInstantiation / instantiationLocation

instantiationLocation

The descriptor instantiationLocation is considered to be an address for a media item. For an organization or producer acting as caretaker of a media resource, instantiationLocation may contain information about a specific shelf location for an asset, including an organization’s name, departmental name, shelf ID and contact information. The instantiationLocation for a data file or web page may include domain, path, filename or html page.

XPATH LOCATION:

/ pbcoreDescriptionDocument / pbcoreInstantiation / instantiationLocation

USAGE RULES:

Occurs:

1 time only

May Contain:

Contained by:

Contained with:


[Any elements used MUST appear in this relative order]

EXAMPLES:

  • <instantiationLocation>Vault: ML007859.121.1.</instantiationLocation>
  • <instantiationLocation>Bay 12, Shelf 21</instantiationLocation>
  • <instantiationLocation>drive2/sourcefiles/20070910/458.wmv</instantiationLocation>

6 responses to “instantiationLocation”

  1. Amanda Raab
    Amanda Raab March 23, 2011 at 7:31 pm |

    Any chance there could be attributes or subelements assigned to instantiationLocation? I’d like to create a hyperlink via this element but the current definition doesn’t seem to allow this. Could there be something equivalent to MODS’s “xlink” attribute?

  2. Peter Pinch
    Peter Pinch March 29, 2011 at 6:12 am |

    In the PBCore 2.0 schema, instantiationLocation is a string, which could be a URL. And in fact, the documentation encourages you to “include domain, path, filename or html page

    Is this adequate, or are you looking for a more complex data type?

  3. Courtney Michael
    Courtney Michael July 18, 2011 at 8:21 pm |

    more complexity would be good because we often have multiple location references. For example I have a shelf ID but then I also have numbers for the shelf, bay and row. I would like to add source attributes to these numbers instead of plugging the word into the value.

  4. Dave Rice
    Dave Rice August 10, 2011 at 5:40 pm |

    A second vote for Amanda’s comment. I’m currently dealing with collections that have human-readable location names which are then assigned to location identifiers. Getting all the necessary info to fit and remain parseable is difficult with only a string field. Additionally if I used something like the shelf location in instantiationLocation then there’s no real way to declare the authority that provided the shelf id to put it in context. In this case, I’m going back to instantiationAnnotations.

  5. Marcos Sueiro
    Marcos Sueiro November 2, 2011 at 4:32 pm |

    And I third that comment. @source, @ref, are needed, and this needs to be repeatable.

  6. Martina McGinn
    Martina McGinn December 14, 2011 at 12:47 am |

    And a 4th vote: many collections have multiple designations for a location

Leave a Reply