Pre-configure DSpace Embargo settings so that it is easier to enable.
---------------------------------------------------------------------
Key: DS-668
URL: http://jira.dspace.org/jira/browse/DS-668
Project: DSpace 1.x
Issue Type: Improvement
Components: DSpace API
Affects Versions: 1.6.2, 1.6.1, 1.6.0
Reporter: Tim Donohue
Fix For: 1.7.0
>From various discussions on 'dspace-tech', there seems to be confusion on how
>to enable / setup embargo settings. There's too many steps involved, and we
>need to simplify it for less-technical folks.
I propose we do the following:
(1) Pre-configure all the "#### Embargo Settings ####" in dspace.cfg. So,
actually ship DSpace with precreated 'terms' and 'lift' fields, which are
pre-configured in dspace.cfg
(2) Pre-configure input-forms.xml with commented-out fields which can be used
to enable embargo. Add a comment to that file that those field(s) need to be
uncommented to fully enable embargo functionality.
After that, we'll just document that people just need to uncomment the embargo
fields in 'input-forms.xml' in order to enable Embargo.
Thoughts? Volunteers to implement?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
