[
http://jira.dspace.org/jira/browse/DS-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10454#action_10454
]
Larry Stone commented on DS-271:
I haven't been following this too closely so I'm not sure how relevant
The custom embargo plugin for my own site (I wrote the prototype
implementation so I've had an advance look..) actually does something
along these lines: It checks one DC metadata field for the embargo
date, and another one for a condition that would place the item under
"permanent embargo"
Hi Andrea:
I'm not clear about how such a proposed change would work: even if we
change the time of policy imposition to when the workspace item is
created, there is no way in the submission UI to manipulate them. To
bring over and expose the parts of the admin UI necessary to manage
policies on t
Note that the GSoC program for this year ends shortly. If you think
you will want to provide feedback on this work please take a look and
send your feedback this week.
Thanks
-AZ
On Mon, Aug 3, 2009 at 11:06 AM, Bojan Suzic wrote:
>
> Dear all
>
> dspace-rest project is about implementing RESTful
Dear all
dspace-rest project is about implementing RESTful service module for Dspace,
allowing users to browse sites and repositories using REST based approach. It
is run as a part of GSoc program.
The page describing endpoints, input and output values and general mappings is
available at [1]
Hi Richard,
I write primary to you as chair of the embargo functionality workgroup
for 1.6
Claudia has recently added a jira issue, DS-267,
http://jira.dspace.org/jira/browse/DS-267
about the opportunities to make modifiable during the submission process
the final permission applied to the item and
