Hello, we have defined a dc.type "Konvolut" for the enclosing entity. Usually the cover page is shown there. Stuff contained within the booklet, folder, casket or whatever it is are devoted separate items in DSpace which point to the enclosing item by a dc.relation.ispartof entry. We did not find a way to point forward from the enclosing item to all items enclosed. Users have to enter the enclosing item first, note the handle ID, then pointing to this item when creating subsequent items for the artifacts enclosed by the "Konvolut".
We dont expect visitors of the archive to discover this metadata structure and use it for their purposes. More likely, they find the cover page, which actually is a Konvolut and search for other items with similar title or just browse the collection by clicking in the breadcrumbs. However, if DSpace would offer a way to present related items in a sensible way one day, the metadata to make it possible would already be there. Other repositories harvesting us could make use of it right away. It is our way of depicting the physical structure of the archive presented within DSpace. E.g. the "Konvolut" may have more detailed information about the place where the physical items is kept, about provenance and so on, whereas the items contained carry descriptions for each picture of an album. So they can be found by full text search. Using a more elaborate community/collection structure would have been an alternative, but it would have caused administrative overhead on our side and just would not have felt right. In the archive, there are books (normal items) and Folders (Konvolut) placed side by side on the same shelf. They all belong to one collection. A structure within DSpace that "does not feel right" in a way would likely have triggered inconsistencies and misunderstandings among users. Bye, Christian See examples here: <http://stadtteilgeschichten.net/browse?value=Konvolut&type=type> <http://stadtteilgeschichten.net/handle/2339/1193?show=full> <http://stadtteilgeschichten.net/handle/2339/1194?show=full> <http://hdl.handle.net/2339/1195> <http://hdl.handle.net/2339/1196> <http://hdl.handle.net/2339/1197> <http://hdl.handle.net/2339/1198> <http://hdl.handle.net/2339/1199> <http://hdl.handle.net/2339/1200> <http://hdl.handle.net/2339/1201> Am 23.02.2017 um 23:40 schrieb Reed, Marianne A. <[email protected]>: > We’ve had similar challenges, Alston, and have had to determine what to do on > a case-by-case basis, since the best practices may vary depending on the > nature of the material. > > For the project you describe, I think that this sounds like a great way to > show the pages of the notebook in their original context, yet include > additional metadata for each page. > > Marianne Reed > Digital Initiatives Coordinator > 450 Watson Library > University of Kansas Libraries > [email protected] > 785-864-8913 > > From: [email protected] > [mailto:[email protected]] On Behalf Of Alston Cobourn > Sent: Thursday, February 23, 2017 3:34 PM > To: DSpace Community <[email protected]> > Subject: [dspace-community] handling complex, multi-part items in DSpace > > Has anyone had experience putting complex, multi-part items in DSpace? For > example, a field notebook with many pages. We consider it very important for > the metadata for each individual page to be made available. We have > considered making each page its own item for that reason but feel that would > be unwieldy because of quantity and while we would record the information > about the book it belongs to in dc.relations fields, it will be harder for > the user to see the relational context because the records between the pages > will not actually be linked. Therefore, we are thinking of making the "item" > be the field notebook as a whole and adding bitstreams for the whole field > notebook as a pdf and a csv file of the metadata for each individual page. > Any thoughts are appreciated. > -- > You received this message because you are subscribed to the Google Groups > "DSpace Community" 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-community. > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "DSpace Community" 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-community. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "DSpace Community" 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-community. For more options, visit https://groups.google.com/d/optout.
