I’m trying to restrict which fields are exported using the bulk metadata export 
function. My goal is to have a csv with only the internal DSpace ID and 
dc.identifier.uri fields in the csv. To that end I’ve tried to set the 
configuration options to ignore all the other fields. However, I’m still 
getting all of the fields when I do an export. I’m using DSpace 3.2.

bulkedit.cfg has the following:

# Metadata elements to exclude when exporting via the user interfaces, or when 
using the
# command line version and not using the -a (all) option.
ignore-on-export = collection, dc.contributor.author[en_US], 
dc.date.accessioned, dc.date.accessioned[], dc.date.available, 
dc.date.available[],  dc.date.issued[en_US], dc.description.abstract[en_US], 
dc.description.advisor[en_US], dc.description.committee[en_US], 
dc.description.degree[en_US], dc.description.department[en_US], 
dc.description.major[en_US], dc.description.provenance[en], 
dc.embargo.liftdate[], dc.identifier.other[en_US], dc.identifier.uri[], 
dc.language[en_US], dc.publisher[en_US], dc.rights[en_US], dc.subject[en_US], 
dc.title.alternative[en_US], dc.title[en_US], dc.type[en_US]

And here’s the head of the resulting export file:

id,collection,dc.contributor.author[en_US],dc.date.issued[en_US],dc.description.abstract[en_US],dc.description.advisor[en_US],dc.description.committee[en_US],dc.description.degree[en_US],dc.description.department[en_US],dc.description.major[en_US],dc.description.provenance[en],dc.embargo.liftdate[],dc.embargo.terms,dc.identifier.other[en_US],dc.identifier.uri,dc.identifier.uri[],dc.language[en_US],dc.publisher[en_US],dc.rights[en_US],dc.subject[en_US],dc.title.alternative[en_US],dc.title[en_US],dc.type[en_US]
"15983","10724/5","Lupis, Giuseppe","2006-05","The study examines the published 
music of Keith Emerson (b.1944) and includes solo piano transcriptions of 
thirteen of his compositions. EmersonÕs music was published on three continents 
over a period of thirty years (1975-2005). Because almost all of it is 
currently out of print, a need exists for a cataloguing and a rediscovery of 
his music. The work is in five chapters. The first, a short biography, examines 
Emerson as a composer. The second addresses the importance of EmersonÕs music. 
The third covers the sources of EmersonÕs published compositions and a 
performance and recording history of EmersonÕs music performed by pianists 
other than the composer. The fourth chapter surveys thirteen compositions which 
appear as solo piano transcriptions in the fifth chapter.","Zimdars, 
Richard","Thomas, Susan||Ball, Leonard||Rivkin, Evgeny||Frazier, 
Ivan","D.M.A.","Music","Music","Made available in DSpace on 
2011-03-03T20:42:36Z (GMT). No. of bitstreams: 1
lupis_giuseppe_200605_dma.pdf: 5227526 bytes, checksum: 
10f2412e920362c100d3a11d41bd09eb (MD5)
  Previous issue date: 
2006-05",,,"lupis_giuseppe_200605_dma","http://hdl.handle.net/10724/9008",,"eng","uga","campus","Keith
 Emerson||Dissertation||Published Music||Rock History||Transcriptions||Solo 
Piano Repertoire||ELP||Emerson Lake & Palmer||Tarkus||Pictures at an 
Exhibition","expanding the solo piano repertoire","The published music of Keith 
Emerson",”Disseration”

Suggestions?
Shawn
------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
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

Reply via email to