You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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...
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.
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.
The text was updated successfully, but these errors were encountered: