We have to import a lot of metadata which will be exported from Aleph's web interface. It exports in some available formats:
http://biblioteca.senado.gov.br:8991/F/MFPJF17G2Q6CQQIC78UC6JN97RVS7YVI2PHPCXUS2XCAR13D93-01362?func=short-mail-0 I am wondering if the given collection should use MARC as the metadata schema, is that a good idea? That should make the import part straightforward (maybe not, there is a LKR field the user wants to break up). Or should it be better to keep the collection schema as DC and make a MARC -> DC conversion? Or something else? I found out that thru greasemonkey i should be able to insert the option for Aleph's internal format that shouldn't need much parsing (some fields are already separated unlike how it appears in MARC). Any idea what is the best route? Thanks a lot for the input, Flavio Botelho ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
