Hi together, We are using DSpace 4.1 and I have a question regarding the Advanced Embargo functionality. During the install of an Item in org.dspace.content.InstallItem.populateMetadata(Context, Item) line 164 the item is checked if there is an embargo. But it uses the old EmbargoManager so it will never find an embargo. The result is that dc.date.available is always the day of the acceptance of an item. Is this a Bug or the expected behaviour? Because in pre DSpace 3.x instances the dc.date.available is set to the embargo lift date when the EmbargoLifter is run and an embargo is lifted. I think that's the way date available should be set.
Regards -- Christian Scheible Softwareentwickler / Abt. Content-basierte Dienste Kommunikations-, Informations- und Medienzentrum (KIM) Universität Konstanz 78457 Konstanz +49 (0)7531 / 88-2857 Raum B 703 ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
