Hi Chris, I think what you are seeing is that "dc.description.provenance" is a hidden field by default, see "metadata.hide" settings in dspace.cfg: https://github.com/DSpace/DSpace/blob/main/dspace/config/dspace.cfg#L927-L943
Hidden fields are only accessible to full Administrators...and therefore, I believe only full Administrators can export them to CSVs (as they are not visible to Community/Collection Admins, etc). This behavior should be the same in 7.x as it was in 6.x (as far as I'm aware, I don't believe this area of the code changed...but I could be wrong). Tim ________________________________ From: [email protected] <[email protected]> on behalf of Chris Clawson <[email protected]> Sent: Thursday, July 7, 2022 1:01 PM To: DSpace Technical Support <[email protected]> Subject: [dspace-tech] Re: Fields available in metadata export 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]<mailto:[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<https://groups.google.com/d/msgid/dspace-tech/41f2e8da-cd8e-4209-a1d9-97b3733bdc72n%40googlegroups.com?utm_medium=email&utm_source=footer>. -- 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/PH0PR22MB3274247BE9D0748152252D45ED879%40PH0PR22MB3274.namprd22.prod.outlook.com.
