Hello DSpace-Community,
we are currently planning to use DSpace as a repository for a reasonably big
(>> 100 TB) collection of images i.e. digitized archival assets.
Right now we need to figure out how to efficiently use the DSpace Content
Object Model (as described in
https://wiki.duraspace.org/display/DSPACE/DSpaceMETSSIPProfile ).
1. For one archival object / digitized asset we do not only have one image file
/ bitstream but four:
1. high resolution TIFF ("master")
2. good resolution JPEG ("usage")
3. lower resolution JPEG ("preview")
4. tiny JPEG ("thumbnail")
2. Users interact with our online finding aid which will have to retrieve the
requested images from DSpace via REST.
3. We could put all four bitstreams, belonging to the same archival item, under
one DSpace Item and place them in different bundles, each of them identifyable
through different tags in "Bundle:" for the different file types. Or we could
just move our currently used archival hierarchy one level up and make every
archival item a DSpace Collection, hence placing every bitstream under its own
DSpace Item with Bundle:ORIGINAL and different DC entries for "Type:".
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.
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.
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.
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.
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.
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.
Any help confirming or disconfirming these assumptions would be of great value
and highly appreciated.
Thanks a lot!
Take care
Nils
- - - - - - - - - - - -
_Referent für Digitalisierung / _Hessisches Landesarchiv
Nils Reichert \
\ Friedrichsplatz 15
Tel.: 06421 9250-108 / 35037 Marburg
--
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.
