On Thu, Oct 25, 2012 at 11:06 PM, Sarah Potvin <[email protected]> wrote:
> 1) ingest an item into DSpace with a METS file
Yes, as detailed above.
> 2) have DSpace crosswalk metadata from the METS file into DIM and
> display/retain this DIM metadata
Yes, that's what happens during import ("ingestion").
> 3) have DSpace store the original METS file
Not automatically, but easy to do. You can attach the original METS
file as a bitstream. It doesn't have to be publicly accessible.
> 4) upon export, have DSpace export a METS file that combines the
> originally-imported METS file, metadata generated upon import (such as
> checksums, bitstream data, provenance metadata, etc.) and stored with the
> item, and any metadata for the item that has been added or edited.
You'd have to do the combination yourself with the original bitstream
you stored. But why use the original METS file when you can have
DSpace to a DIM->METS transformation ("dissemination"), which is a
standard procedure?
Regards,
~~helix84
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
