Hi Stefan, I believe the Bundle name for bitstreams ingested via SWORD (or other packaging tools) can be specified in the "USE" attribute of a METS <fileGrp>. You can see this in the Example METS file for SWORD at: https://github.com/DSpace/DSpace/blob/master/dspace-sword/example/mets.xml#L133
Notice, in this case USE="CONTENT". which means these bitstreams will be added to the CONTENT bundle. If you change it to a different value, it should instead add those bitstreams to a different Bundle. This is achieved because SWORD (both versions) actually just uses our DSpaceMETSIngester (which is also used by commandline tools that ingest METS). In the DSpaceMETSIngester, after a bitstream is found in the METS file, this "finishBitstream" method is called: https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/src/main/java/org/dspace/content/packager/DSpaceMETSIngester.java#L238 You'll notice in that method, it checks the "getBundleName()" provided by the METS file itself. That method looks at the "USE" attribute: https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/src/main/java/org/dspace/content/packager/METSManifest.java#L491 Hopefully that helps, - Tim On Fri, Oct 19, 2018 at 7:10 AM Stefan Kombrink <[email protected]> wrote: > Hi euler, > > thanks for your reply. I can't use xmlui though, I need to make it work > via sword (or any other automated way) somehow. > > greets Stefan > > On 10/19/18 11:59 AM, euler wrote: > > Hi, > > > > If you are using XMLUI, there is a setting there in dspace.cfg: > > > > # Determine which bundles administrators and collection administrators > > may upload > > # into an existing item through the administrative interface. If the > > user does not > > # have the appropriate privileges (add & write) on the bundle then that > > bundle will > > # not be shown to the user as an option. > > #xmlui.bundle.upload = ORIGINAL, METADATA, THUMBNAIL, LICENSE, CC-LICENSE > > > > The bundles above (in uppercase letters) are the default bundles which > > you can upload as bitstream. You just have to select the appropriate > > bundle when submitting, ie select Licenses instead of Content Files > > (default) when uploading the file. See attached screenshot. > > > > Hope this helps. > > > > upload-license.PNG > > > -- > Stefan Kombrink > Universität Ulm > Kommunikations- und Informationszentrum (kiz) > Abteilung Informationsmedien > +49-731-50-31482 <+49%20731%205031482> > > -- > All messages to this mailing list should adhere to the DuraSpace Code of > Conduct: https://duraspace.org/about/policies/code-of-conduct/ > --- > 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 post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. > -- Tim Donohue Technical Lead for DSpace & DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
