> Amanda > > this sounds tricky > > I remember that Andrea Schweer gave a poster presentation at OR 2015 about a > Symplectic pitiful regarding changing items after they were pushed from > Symplectic to a DSpace instance. She implemented some custom stuff - but > essentially I remember the advise being: avoid at all cost. > > We are about to start with Symplectic here at Princeton; but since we haven’t > started yet I have no detailed advise > > Monika
________________ Monika Mevenkamp mo.me...@gmail.com > On Feb 1, 2016, at 12:35 PM, Monika C. Mevenkamp > <moni...@exchange.princeton.edu> wrote: > > Amanda > > this sounds tricky > > I remember that Andrea Schweer gave a poster presentation about a Symplectic > pitiful regarding changing items after they were pushed from Symplectic to a > DSpace instance. She had to implement some custom stuff - but essentially I > remember the advise being: avoid at all cost. > > We are about to start with Symplectic here at Princeton; but since we haven’t > started yet I have no detailed advise > > Monika > > > — > Monika Mevenkamp > Digital Repository Infrastructure Developer > Princeton University > Phone: 609-258-4161 > Skype: mo-meven > >> On Feb 1, 2016, at 12:05 PM, Tim Donohue <tdono...@duraspace.org >> <mailto:tdono...@duraspace.org>> wrote: >> >> Hi Amanda, >> >> Do you (or anyone else) know how Symplectic Elements is pulling content from >> DSpace? >> >> In general, this sounds like it *might* be more of an issue with how >> Symplectic Elements is pulling in DSpace content, and you may wish to talk >> to them about the possibility of pulling in non-ORIGINAL bundles from your >> non-public DSpace. It's possible it may something they can configure on >> their end. >> >> - Tim >> >> On 1/31/2016 5:48 PM, Amanda Curnow wrote: >>> [apologies for cross-posting] >>> >>> hi all, >>> >>> I'm looking for technical advice from folks savvy with Dspace 5 and >>> Symplectic Elements. >>> >>> We have academics deposit two categories of documents into Symplectic >>> Elements. (1) Full text content of the research output (be that published >>> or accepted version etc) and (2) 'Evidence' which may be for example, the >>> conference programme they presented at, or an email asking them to be a >>> keynote, or even permission from the publisher that the output can be made >>> Open Access. >>> >>> Our Research Office want to be able to store this Evidence file >>> electronically in the non-public DSpace instance (connected to Symplectic), >>> but we don't want it harvested into the public Dspace instance (MRO). >>> We set up a curation task to move any bitstreams categorised with the tag >>> 'Evidence' into another bundle within the non-public Dspace. This works >>> perfectly in that the files in this bundle do not get harvested. >>> >>> However it means that the files are no longer visible/viewable in the >>> Symplectic Elements record, which is crucial to the Research Office staff. >>> >>> Does anyone have any thoughts on how non-ORIGINAL bundles in Dspace might >>> still be viewable in Symplectic? >>> >>> I hope that makes sense. >>> Am running Dspace 5.4 on both instances, Symplectic Elements 4.12.0.579 >>> and RT4DS version 1.1 >>> >>> Amanda >>> >>> >>> -- >>> 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 >>> <mailto:dspace-tech+unsubscr...@googlegroups.com>. >>> To post to this group, send email to dspace-tech@googlegroups.com >>> <mailto:dspace-tech@googlegroups.com>. >>> Visit this group at https://groups.google.com/group/dspace-tech >>> <https://groups.google.com/group/dspace-tech>. >>> For more options, visit https://groups.google.com/d/optout >>> <https://groups.google.com/d/optout>. >> >> -- >> Tim Donohue >> Technical Lead for DSpace & DSpaceDirect >> DuraSpace.org <http://duraspace.org/> | DSpace.org <http://dspace.org/> | >> DSpaceDirect.org <http://dspacedirect.org/> >> >> -- >> 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 >> <mailto:dspace-tech+unsubscr...@googlegroups.com>. >> To post to this group, send email to dspace-tech@googlegroups.com >> <mailto:dspace-tech@googlegroups.com>. >> Visit this group at https://groups.google.com/group/dspace-tech >> <https://groups.google.com/group/dspace-tech>. >> For more options, visit https://groups.google.com/d/optout >> <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.
