Title: Message Title
|
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Unassigned
|
|
Components:
|
SWORD
|
|
Created:
|
21/Jan/14 11:01 AM
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Ian Stuart
|
|
Whilst SWORD (as a transport mechanism) and METS (as a Metadata Encoding Schema) are content-neutral, the ingester class within DSpace that handles METS packages has been hard-coded for one specific
content-model.
This makes is difficult to extend DSpace to ingest data used by other systems.
It makes sense for the METS Ingester to read a configuration file to determine which profiles are acceptable, and then to select the appropriate XSLT Cross-Walker to map from <external supplier> into
<repository schema>
I am proposing this, as I am trying to create an importer to ingest a METS package that doesn't contain the "epdcx" data-payload as defined in the "DSpace METS SIP Profile" definition.
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
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-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
