Hi Monika, I can answer your question about the multiple collections. Symplectic provides a script (written in Java) called "IngestMapping" that takes a collection mapping file as input and will configure the Symplectic DSpace plugin to automatically attach a submitted Symplectic item to the correct DSpace collections.
The Symplectic collection mapping file defines a mapping between Symplectic group keys (e.g. /Your Institution/Faculty/Department/Research Group) to DSpace collection handles (e.g. 123456/21). In the case that an article belongs to multiple Symplectic groups (and thus has multiple group keys) this will automatically result in a DSpace item attached to all matching DSpace collections. Best regards, Tom [image: logo] *Tom Desair* *250 Lucius Gordon Drive, Suite B-3A, West Henrietta, NY 14586* *Esperantolaan 4, Heverlee 3001, Belgium* www.atmire.com <http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=tomd> 2016-03-09 19:22 GMT+01:00 Monika Mevenkamp <mome...@gmail.com>: > We are getting ready to setup a symplectic instance with a dedicated > dspace repository instance. > > In the public facing repository UI we want to show a list of collections > representing departments/groups each containing articles of affiliated > faculty. We expect that metadata about an articles affiliation to > departments will be somehow available. Of cause there will be special > cases like articles jointly published by several faculty members from > different departments. We’ll have to work out what to do about authors who > are appointed at multiple departments. > > As per documentation Symplectic pushes all discovered articles into the > workflow of a dedicated collection. Thus the main issue is to figure out > how to shepherd articles from this one collection into the desired > department collection(s). Preferable we want to automate this. Reading > through the DSpace documentation I discovered AbstractProcessingStep. > Implementing a specialized step that reassigns the destination collection > might be a possible route. Alternatively a dedicated curation task could > look through submitted items and reassign them. Any other better options ? > > I’d like to hear what other institutions do ? Any tips, tricks code, pit > falls to avoid ? > > Thanks > > Monika > > > ________________ > Monika Mevenkamp > Digital Repository Infrastructure Developer > Princeton University > Phone: 609-258-4161 > Skype: mo-meven > > > > -- > 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 dspace-tech+unsubscr...@googlegroups.com. > To post to this group, send email to dspace-tech@googlegroups.com. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. > -- 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 dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
