I checked this file inside my DS 7.2 installation. Here is the entry I would expect to control the terms:
# Metadata elements to exclude when exporting via the user interfaces, or when using the # command line version and not using the -a (all) option. # bulkedit.ignore-on-export = dc.date.accessioned, dc.date.available, \ # dc.date.updated, dc.description.provenance Please notice this feature is already commented out, yet the terms are not being exported in the CSV. Is this a 7.2 bug or is the export of these terms also controlled somewhere else? On Thursday, July 7, 2022 at 11:34:45 AM UTC-4 [email protected] wrote: > The dc.description.provenance is a hidden field by default so it is not > exported by default in the XMLU interface for DSpace 6.3. > https://wiki.lyrasis.org/display/DSDOC6x/Batch+Metadata+Editing#BatchMetadataEditing-WebInterfaceExport > > has instructions for including additional fields.It looks like the > configuration file for this is [dspace]/config/modules/bulkedit.cfg . > > Anne > > On Wednesday, July 6, 2022 at 2:21:00 PM UTC-4 Chris Clawson wrote: > >> Do I remember the dc.provenance being exported with metadata in earlier >> versions? When I export collection metadata in DS 7.2, I no longer see any >> fields included which report the original bitstream filenames, which is >> important to us. >> Might someone please describe the location and config files that control >> which fields are exported to CSV? How may I configure this? >> > -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/41f2e8da-cd8e-4209-a1d9-97b3733bdc72n%40googlegroups.com.
