Hello Nils, I've done my best to answer your questions inline below...
On Mon, Oct 29, 2018 at 7:09 AM <[email protected]> wrote: > Both options have their pros and cons. To make an informed decision it > would be very helpful if our current assumptions about how bundles work are > true: > 1. A bundle is more or less a group of files inside a DSPace Item. > Correct. > 2. The standard way to do things is to only use Bundle:ORIGINAL. There are > no other bundle types available through the UI and, even more important, > other bundle types cannot be accessed/selected for uploads via the > addItemBitstream method in the REST API. > Correct, unless you modify the UI. It is possible, for example, in the XMLUI to customize your theme to display files from other Bundles. But, by default, DSpace only displays the ORIGINAL bundle > 3. You cannot change, alter or add to bundles once they are created. You > also cannot move a bundle into another bundle or item after creation. > Technically false, but it depends on what you mean by this. You can change/alter/add to bundles both through the UI (Edit Item screens) and through the Java API. However, the functionality of the current REST API is very limited in this area, and I don't think these features are available in the REST API yet. I don't believe you can move Bundles, unless you did so via custom database queries (not recommended). > 4. Bundles can be created through the Simple Archive Format or through > METS while importing or exporting to/from DSPace. The Bundle explicitly > defined inside the SAF/METS files will be created by DSpace without > further questions. > I'm not entirely sure that Bundles are auto-created....and it may depend on the import mechanism. You may want to simply test this...from the code though, it looks to me like the Bundle may need to exist prior to running Simple Archive Format or METS import. > 5. You cannot access a bundle directly but will always have to access the > item first. An item can be accessed through its UUID or its handle. You can > get a list of an items contents and access the bitstreams of the bundles > listed there. Therefore, the bundle is received as text when the item is > queried. > Depends on what you mean by "access". Bundles are actual objects in the database / Java API layer. So, you can access them in the Java API. But, in the UI and REST API, they usually just appear as "text". You are correct though that an Item can always be accessed through its UUID or handle. > 6. There is no special protection for bundles. DSpace does not provide a > fine-grained access control allowing access to a single bundle (let's say > "usage") but not another (say "master" ) belonging to the same Item. > > DSpace does not provide a special way to pre-configure access rights based on a bundle's "name". However, you *can* change access rights per bundle (after submission). Bundles are listed in the "Authorization Policies" of an Item, if you go to the "Edit Item" screen, and you can change their permissions like any other object. Hopefully that helps! Let us know on this list if you have more questions! Tim -- 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.
