Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve granularity of instantiationLocation #97

Open
caseyedavis12 opened this issue Dec 5, 2014 · 1 comment
Open

Improve granularity of instantiationLocation #97

caseyedavis12 opened this issue Dec 5, 2014 · 1 comment
Labels

Comments

@caseyedavis12
Copy link

I know that this is after the call for issues, but I was looking at the PBCore website today and noticed FOUR votes for this dating back to 2011! Make that five, if you include me.

See comments about this on the PBCore website: http://pbcore.org/v2/elements/pbcoredescriptiondocument/pbcoreinstantiation/instantiationlocation/

In short:
-Add attributes @source @ref @Version @annotation
-Add subelements, more complexity because we often have multiple location references. An example would be shelf ID, and numbers for shelf, bay and row.
--Currently, getting all of the data to fit and remain parseable is difficult without attributes and subelements.

@AllisonAnn
Copy link

hi Casey -

I agree that any missing attributes should be added to the existing
location element, but I'd be cautious about adding sub elements for
refined/specific location information. Is this really necessary or
advisable (do most institutions really want the public to know their
specific shelf locations)?

From experience, I can say that locations for any given item can change
quite a bit (there is no such thing as a permanent location for the most
part), and keeping locations updated is always a struggle (especially for
those archives/museums who aren't using a barcoding system yet). So, I am
not really in favor of this type of schema enhancement, because I don't
think it's necessary or adds anything useful.

If the schema is mainly for data exchange, who needs this precise shelf
location information anyway, especially if it might be outdated?
But again, I can always be persuaded by a good argument...

Allison

On Fri, Dec 5, 2014 at 2:08 PM, Casey Davis notifications@github.com
wrote:

I know that this is after the call for issues, but I was looking at the
PBCore website today and noticed FOUR votes for this dating back to 2011!
Make that five, if you include me.

See comments about this on the PBCore website:
http://pbcore.org/v2/elements/pbcoredescriptiondocument/pbcoreinstantiation/instantiationlocation/

In short:
-Add attributes @source https://github.com/source @ref
https://github.com/ref @Version https://github.com/version @annotation
https://github.com/annotation
-Add subelements, more complexity because we often have multiple location
references. An example would be shelf ID, and numbers for shelf, bay and
row.
--Currently, getting all of the data to fit and remain parseable is
difficult without attributes and subelements.


Reply to this email directly or view it on GitHub
#97.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants