I'm using dc.date.available as the date an item was purchased (anywhere
from the 1940's to the 1990's). When I import a CSV file, I get two entries:
dc.date.available 1968-05-27 -
dc.date.available 2014-02-05T15:26:08Z
I am also using dc.description.provenance (for actual provenance, prior
owner(s)) and get
dc.description.provenance Daniel Webster (1782-1852) -
dc.description.provenance Made available in DSpace on
2014-02-05T15:26:10Z (GMT). No. of bitstreams: 0 Previous issue date: 1824
That is, this item belonged to Daniel Webster (yes, that Daniel Webster).
So, I'm wondering if I'm using the wrong DC metadata definitions or if
there is some way to prevent the import from the double whack?
What I want is a book published in 1824, purchased in 1965 and
previously owned by one or more individuals to be recorded as such (and
I don't really give a hoot when it was inserted in DSpace). Am I using
the wrong DC codes? Any suggestions about perhaps using different DC
codes to describe the item?
I'm kind of wondering if dc.date.accessioned might be the better choice
for dc.date.available but I'm not sure and would appreciate any hints.
Thanks.
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette