Hi Hans, I guess the duplicate policies is something that was meant to be fixed, but wasn't [1]. I'm not sure how it can happen that there is no user set, but I think database constraints would make sure you cannot have two rows with the same (resource_type_id, resource_id, action_id, eperson_id).
[1] https://github.com/DSpace/DSpace/blob/dspace-4_x/dspace/etc/postgres/xmlworkflow/workflow_migration.sql#L211 Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
