You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The iso2geoBL.xsl transforms the publisher field to the multi-valued element dc_publisher_sm.
However, the official GBL Metadata Schema indicates the singular dc_publisher_s.
Since the Big Ten project uses both the XSLT with GIS records, and NYU's plugin for Omeka with maps, we discovered that we had a mix of dc_publisher_s and dc_publisher_sm in our Solr. We would prefer to use dc_publisher_sm. Any reason why we wouldn't want to enable having multiple publishers?
The text was updated successfully, but these errors were encountered:
We're not using iso2geoBL.xsl in our production environment (we go from ISO to MODS to GeoBlacklight) so our instance uses dc_publisher_s. I don't see a reason, however, that you couldn't use multiple publishers. You just need to change the view logic in GeoBlacklight (likely just in catalog_controller.rb). BTW, our MODS to GeoBlacklight XSLT is here -- https://github.com/sul-dlss/gis-robot-suite/blob/master/lib/xslt/mods2geoblacklight.xsl
The iso2geoBL.xsl transforms the publisher field to the multi-valued element dc_publisher_sm.
However, the official GBL Metadata Schema indicates the singular dc_publisher_s.
Since the Big Ten project uses both the XSLT with GIS records, and NYU's plugin for Omeka with maps, we discovered that we had a mix of dc_publisher_s and dc_publisher_sm in our Solr. We would prefer to use dc_publisher_sm. Any reason why we wouldn't want to enable having multiple publishers?
The text was updated successfully, but these errors were encountered: