Hi Monika,
We do this manually because we want to make sure that only full-text papers
with appropriate copyright / publisher permissions get made public (and do some
basic metadata quality control). So our process is that everything is pushed
into a non-public "Symplectic" collection. In workflow, repository staff check
it, (if necessary go back to Elements to fix any major metadata issues), and
then either:
a) approve it into the hidden "Symplectic" collection, if copyright doesn't
allow us to make the full-text open access; or
b) approve it into one or more public departmental collections. Because I don't
do this personally I forget whether we have to also manually edit permissions.
Automating it wouldn't work for our environment but we do pull data in from
Elements about faculty/department via the crosswalk into a local DSpace field
lu.contributor.unit. As an example:
In the feed from Elements we have:
<pubs:organisational-details>
<pubs:group org-id="1">/LU</pubs:group>
<pubs:group org-id="8">/LU/ABCD</pubs:group>
<pubs:group org-id="21">/LU/ABCD/WXYZ</pubs:group>
[... and more groups if authors from other depts are involved ...]
</pubs:organisational-details>
(where LU is the institution, ABCD is the faculty, WXYZ is the department).
Our xwalks_custom.xsl crosswalk has:
<xsl:template match="pubs:organisational-details" mode="feed">
<xsl:for-each select="pubs:group">
<dim:field mdschema="lu" element="contributor" qualifier="unit"
lang="en">
<xsl:apply-templates select="." mode="render_with_dictionary">
<xsl:with-param
name="dictionary-name">pubs:group</xsl:with-param>
</xsl:apply-templates>
</dim:field>
</xsl:for-each>
</xsl:template>
(There may be additional configuration somewhere to allow you to use data from
the full feed, it's been a while since I set this up.)
And our xwalks_config.xsl has:
<crosswalks:dictionaries>
<crosswalks:dictionary elements="pubs:group">
<crosswalks:entry elements="/LU" dspace="Lincoln University" />
<crosswalks:entry elements="/LU/ABCD" dspace="ABCD Faculty" />
<crosswalks:entry elements="/LU/ABCD/WXYZ" dspace="WXYZ Department"
/>
[...]
</crosswalks:dictionary>
</crosswalks:dictionaries>
Which results in DSpace:
lu.contributor.unit Lincoln University
lu.contributor.unit ABCD Faculty
lu.contributor.unit WXYZ Department
[...]
...So that's the Elements and Repository Tools side of things - from there
hopefully someone more familiar with DSpace capabilities can help with the
workflow issues...
Just to note that because Elements provides data on groups at all levels of the
organisation, either:
a) the workflow will have to only take account of the metadata values that
match up with an existing collection, or
b) you'll need to fine-tune your crosswalk so that it only passes through the
values that you want the workflow to action.
Deborah
-----Original Message-----
From: dspace-tech@googlegroups.com [mailto:dspace-tech@googlegroups.com] On
Behalf Of Monika Mevenkamp
Sent: Thursday, 10 March 2016 7:23 a.m.
To: DSpace Tech <dspace-tech@googlegroups.com>
Subject: [dspace-tech] Push Symplectic articles to multiple collections ?
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.
________________________________
P Please consider the environment before you print this email.
"The contents of this e-mail (including any attachments) may be confidential
and/or subject to copyright. Any unauthorised use, distribution, or copying of
the contents is expressly prohibited. If you have received this e-mail in
error, please advise the sender by return e-mail or telephone and then delete
this e-mail together with all attachments from your system."
--
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.
