Hi Joachim, I don't know answers to all your questions, I hope someone else will competently answer them. I have just a few related comments.
1) ResourcePolicies _can_ be assigned to EPersons. It's helpful to look at the API JavaDocs, also available here: http://demo.dspace.org/javadocs/3/apidocs/ Look at the ResourcePolicy class, setEPerson() method. 2) As you surely noticed (because you proposed a solution), currently EPersons are in no way tied to authors in metadata (dc.contributor.author). I hope that we can work in the 4.0 development cycle to address this as part of the "metadata for all DSpaceObjects" proposal, so that authors can be expressed as objects (EPersons) and have their own metadata. The "metadata improvements" topic will be discussed as part of a DSpace Futures call on March 20, so you're welcome to join in and express your use case and expectations. 3) You can create a ResourcePolicy for an EPerson, but I'm not sure if it works for an item - the smallest object I'm sure works is a collection. The API specifies a resource (a DSpaceObject) as the object of the RP, so the syntax allows you to express even for example an EPerson-EPerson ResourcePolicy, but I'm not sure there is any semantics defined for that. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ 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
