Thank you very much Terry, we'll be studing the functionality of this class.
Meantime, we don't know if is there some problem with the interface, it looks that when you use the advanced embargo policies form for a bitstream, the only way to do so is modifying the files in the submission, and after that there is no interface to modify these policies (we've tried with Mirage and Mirage2). The authorization button for the bitstream is not shown updating the item / files option. Someone could confirm that this is the expected behaviour? We are trying to determine if is there some configuration problem. 2016-06-01 13:02 GMT-03:00 Terry Brady <[email protected]>: > You can write code to implement your own interpretation of an embargo > policy. > > You would need to extend the following class: > https://github.com/DSpace/DSpace/blob/master/dspace-api/src/main/java/org/dspace/embargo/DefaultEmbargoSetter.java > > You then register your customization in the config gile > https://github.com/DSpace/DSpace/blob/master/dspace/config/dspace.cfg#L686-L690 > > If you look into the code above, you will see that it updates the > resourcepolicy table based on the embargo policy. Assets under embargo are > restricted using resource policies. > > Terry > > On Wed, Jun 1, 2016 at 7:19 AM, <[email protected]> wrote: > >> Hi all >> >> We'll use the advanced policies form for the bitstreams, that is only >> accesible via Edit and after uploading the file (in difference with basic >> form) >> >> We have doubts about this paragraph in the documentation >> >> "...The Pre-DSpace 3.0 embargo functionality (see below) has been >> modified to adjust the policies setter and lifter. These classes now also >> set the dates within the policy objects themselves in addition to setting >> the date in the item metadata..." >> >> Does it means that if we define the old >> >> # DC metadata field to hold the user-supplied embargo terms >> embargo.field.terms = SCHEMA.ELEMENT.QUALIFIER >> >> # DC metadata field to hold computed "lift date" of embargo >> embargo.field.lift = SCHEMA.ELEMENT.QUALIFIER >> >> The application will fill these metadata with the embargo end date? >> Is there a way that the user define the policies using the form and the >> metadata about embargo get filled automatically or should we recommend to >> our users to insert the embargo end date. >> >> Thanks in advance >> RH team >> >> -- >> You received this message because you are subscribed to the Google Groups >> "DSpace Technical Support" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at https://groups.google.com/group/dspace-tech. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Terry Brady > Applications Programmer Analyst > Georgetown University Library Information Technology > https://www.library.georgetown.edu/lit/code > 425-298-5498 (Seattle, WA) > -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
