[there is a need for multiple metadata schemas in batch import] It sounds like you are using the Item Importer. It appears that there is an undocumented way to import metadata expressed in other schemae. The importer always looks for 'dublin_core.xml', but it also looks for any file whose name begins 'metadata_' and loads it in the same way. The 'dublin_core' element in a metadata file appears to take an optional attribute 'schema' naming the schema which defines the metadata expressed in the file.
You would need to register the additional schema and the elements and qualifiers which it defines. This can be done using the administrative interface. It can also be done using the method found in the Ant build.xml script under the 'load_registries' target if the definitions are many. (If you do build a metadata registry file for any additional schema, it would be kind of you to make it available somewhere, such as the DSpace Wiki, for others to use.) I have only just today discovered these features in the code while checking my understanding of the Item Importer; I've never used them, although I do use the Item Importer. I think many would agree that additional concepts should not be forced into DSpace's notion of Dublin Core, but should be provided as a distinct schema. -- Mark H. Wood, Lead System Programmer [email protected] Friends don't let friends publish revisable-form documents.
pgpe4IdOBZEcI.pgp
Description: PGP signature
------------------------------------------------------------------------------ Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
