Title: Message Title
|
|
Just adding some detail... At the start of Java class DSpaceMETSIngester there is a hard coded test:- If manifest profile != "DSpace METS SIP Profile" "METS has unacceptable PROFILE value, profile="" + profile So if you have something else in your Mets package then Dspace will complain. This goes back to the days when the only Mets package DSpace could handle was that defined in the DSpace METS SIP Profile. In fact DSpace can handle a number of different metadata schema other than that dictated by the profile (which I suspect is Mods rather than EPDCX). The test should be changed to read a list of acceptable profiles from config. Cheers, Robin.
|
|
|
|
|
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 configuratio...
|
|
|
|
------------------------------------------------------------------------------
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