On 31 March 2010 20:35, Richard Rodgers <rrodgers@mit.edu> wrote:
Hi Hilton:

Not really - the assumption of the embargo system is that once content has been made generally available,  it no longer makes sense to embargo it (since embargo traditionally means withholding exposure until some future time, then exposing it). So it really isn't the same as access restriction, which can be accomplished with standard DSpace administrative tools [and admin changes can me made anytime].

Does that make sense?
Yes. But and there is always a but. What we did before 1.6.0 was to remove the binary object. Now we want to restore them but with an embargo. How do we do that ? See: http://ir.sun.ac.za/wiki/index.php/Asset_Embargo. Check procedure - option b. Will this work ?

Cheers

hg.


Thanks,

Richard

On Mar 31, 2010, at 1:20 PM, Hilton Gibson wrote:

Hi All

With respect to older items already submitted, can one impose an embargo on them without a migration and re-submission ?

Cheers

hg.


On 31 March 2010 16:21, Richard Rodgers <rrodgers@mit.edu> wrote:
Hi Jason:

One thought: have you added those fields to your input-forms.xml? In other respects, the embargo fields behave just like any other metadata, and can be added to the default set - or any collection-specifc set - of metadata fields  used in web submission. The tech doc has instructions on managing input-forms.

Hope this helps,

Richard R

On Mar 31, 2010, at 10:02 AM, Jason Fowler wrote:

> Hi all,
>
> I am testing DSpace 1.6 before we migrate to it. I believe I have the dspace.cfg set up correctly, and I have added dc.embargo.terms and dc.embargo.liftdate to my metadata registry.
>
> However, nothing shows up in the submission workflow in any of my xmlui themes, or in jspui. Are there additional changes that I need to make in order to enable this within the workflow? Can someone explain what those are?
>
> Thanks,
>
>
> Jason Fowler, CA, MSLS
> Archives and Special Collections Librarian
> The Southern Baptist Theological Seminary
> Vice President, ALABI
> jfowler@sbts.edu
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> DSpace-tech mailing list
> DSpace-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech


------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech



--
Systems Administrator
Library and Information Services
Stellenbosch University

http://www.sun.ac.za
http://library.sun.ac.za
http://scholar.sun.ac.za
http://ubuntu.sun.ac.za




--
Systems Administrator
Library and Information Services
Stellenbosch University

http://www.sun.ac.za
http://library.sun.ac.za
http://scholar.sun.ac.za
http://ubuntu.sun.ac.za