Folks, We're migrating away from custom metadata fields in our DSpace 3.3 install and I've been asked to provide both the old and new metadata in Search and Browse conditions.
Specifically, here are two examples of old and new: dc.contributor.author dc.creator (standard) dc.date.published dc.date.issued (standard) Without changing any settings to support the "new" (standardized) metadata fields, batch uploads where dc.creator is used to hold author info means those authors won't show up when browsing by author. Likewise, items which use dc.date.issued rather than dc.date.published will turn up in search results with empty dates associated with those items. I can easily change every instance of dc.contributor.author and dc.date.published in dspace.cfg with an index update (and database content migration) for complete changeover. However, there's more at stake and I've been asked not to do a full conversion so that it can be managed in stages. There-in lies the problem. I have not been able to get two instances of metadata fields to play nicely together in Browse and Search for publication date and author. Is it even possible to configure for more than one instance? From what I'm seeing, it looks like a one-to-one mapping. Regards, -Jeff ------------------------------------------------------------------------------ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
