Hi, I've got a development instance where we uploaded a few hundred items (in one community and several collections). Our editors spent some time manually uploading bit streams to many of these items. Now I want to migrate the community and its hierarchy to the production instance. We can't use the CSV via "Export Metadata" because of the bit streams, so I've been looking at using AIP, ie:
dspace packager -s -a -t AIP -e m...@us.org -p 10568/0 33474.zip
This works great, but the resulting items now have two of each of the
following fields:
- dc.date.accessioned
- dc.date.available
- dc.identifier.uri
I can't figure out a work flow that doesn't produce this effect...
Thanks,
--
Alan Orth
alan.o...@gmail.com
http://alaninkenya.org
http://mjanja.co.ke
"I have always wished for my computer to be as easy to use as my telephone; my
wish has come true because I can no longer figure out how to use my telephone."
-Bjarne Stroustrup, inventor of C++
GPG Public Key: 0xf92c4bd91084bb5de14e20be9470dd588dd1026c
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
