On Wed, Sep 08, 2010 at 06:18:18PM -0400, Richard Rodgers wrote: > If you look at the class DefaultEmbargoSetter (in org.dspace.embargo) the > method > 'parseTerms' creates the lift date out of what EmbargoManager passes it > (which is the contents > of the metadata field configured for the 'terms'), and the next method in > that class > 'setEmbargo' does the setting - which simply consists of removing the read > policies > on the bitstreams. > > Does that help, or further confuse?
Neither, actually. That much I had worked out. What I was wondering is: how did the terms get set in the first place? The documentation is silent there. > To get embargo working, you just need to make sure that the > embargo.terms & embargo.lift properties are configured, Done, but made no visible difference (except that 'dspace embargo-lifter' no longer complains). > and they point to metadata fields that exist, Done, but made no visible difference. > and are in input forms, etc Thanks, this is what I was missing: stock DSpace doesn't do anything about marking an item *to be embargoed* (there is no code which inserts embargo terms automagically); I have to add something to the input forms, or (I think?) set up a template item. -- Mark H. Wood, Lead System Programmer [email protected] Balance your desire for bells and whistles with the reality that only a little more than 2 percent of world population has broadband. -- Ledford and Tyler, _Google Analytics 2.0_
pgp3F9ErmsbqA.pgp
Description: PGP signature
------------------------------------------------------------------------------ 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-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
