On Wed, Sep 23, 2015 at 5:38 PM, Francis Brouns <[email protected]> wrote:
> When I understand correctly, embargo now functions with a date on the > resource policy. How do I set those to indicate a 'forever' embargo? > Correct. If you have 0 policies on an item, it's not accessible (accessible only to administrators). If you add a single policy for the group Anonymous with a start date in the future, it will take effect starting on that date, i.e. inaccessible now, accessible to all users from start date. You'll want to leave end date unspecified (null), otherwise the policy would be only valid until the end date, thus making the item inaccessible again. java.lang.IllegalArgumentException: Embargo lift date must be in the > future, but this is in the past: 2015-09-01 > You should lift using the old lifter these before migrating them. If they were already lifted, check whether they had a correct resourcepolicy assigned (with a start/end date). If not, it may be a forgotten case in migrate-embargo - report a bug. java.sql.SQLException: Year out of range. > Obviously, a date is expected here. java.lang.NullPointerException > Please turn up log level to DEBUG [1] and watch your log for SQL queries prepended by: "Running query " This seems like another corner case was overlooked in migrate-embargo. It seems like the argument (e.g. :1) in the SQL is not available (null) for that particular item. [1] https://wiki.duraspace.org/display/DSPACE/Troubleshoot+an+error Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- 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 http://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
