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 [email protected] <mailto:[email protected]>. To post to this group, send email to [email protected] <mailto:[email protected]>.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

--
Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | 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 [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.

Reply via email to