RE: [dspace-community] Digest for dspace-community@googlegroups.com - 2 updates in 2 topics
WARD Pauline
Thanks very much Maureen. I have a question for folks about usage, if anyone has a view please – We’re currently upgrading to version 6 of DSpace, from version 5, and it seems some of our embargo functionality and processes will probably need to change.
1. We’ve always let the users set the dc.date.embargo field for their item when they submit a deposit. And when that embargo date comes around, DataShare has a cron job which automatically deletes that field and replaces it with a dc.date.available field containing today’s date. We’ve seen information that DSpace’s embargo-lifter script is going to be switched off at some time, and we don’t know for sure whether our cron job uses embargo-lifter, and whether we’re going to have to start doing this two-step process (deleting embargo date and adding date available) manually for every embargo that previously would just expire automatically.
2.
Whereas, we know that the availability of the bitstreams is taken care of by the policies, when the embargo expires automatically.
So we’re not worried about that. But just for completeness – we are adjusting our process to manually edit the read policies through the authorizations control instead of using the field for bitstream embargo date, which has been disabled so it’s not editable
in the demo version of DSpace 6 that we’re running.
Would be interested to hear whether others are manually tracking when their embargo dates will expire etc as I’ve described in (1) above, or are you not using dc.date.embargo at all?
We’re trying to spend less of our time re-inventing the wheel, but we’re not sure any more which bits of the wheel we got came from our previous developer and which are out-of-the-box DSpace.
Best regards,
Pauline
Pauline Ward
Research Data Support Assistant, University of Edinburgh
https://www.ed.ac.uk/information-services/research-support/research-data-service
I’m working from home full time.
From: dspace-c...@googlegroups.com <dspace-c...@googlegroups.com>
Sent: 08 December 2020 00:13
To: Digest recipients <dspace-c...@googlegroups.com>
Subject: [dspace-community] Digest for dspace-c...@googlegroups.com - 2 updates in 2 topics
This email was sent to you by someone outside the University.
You should only click on links or attachments if you are certain that the email is genuine and the content is safe.
· DCAT Meeting: DSpace 7 Documentation Planning Sprint, December 8th, 16:00 UTC/GMT - 11:00 EST - 1 Update
· Restoration of sub-community page - reg - 1 Update
|
"Maureen P. Walsh" <wals...@gmail.com>: Dec 07 10:41AM -0500
|
|
"siva...@gmail.com" <siva...@gmail.com>: Dec 06 07:46PM -0800
|
|
You received this digest because you're subscribed to updates for this group. You can change your settings on the
group membership page. |