I realize now I may have mislead you with my previous post as I just realized I'm still working on version 3.4.1 (which clearly had some issues with FedoraRIAttributeFinder PIDs - by not splitting the resource ID)
This was changed in 3.4.2 using subjects instead of PIDs (to include datastreams etc...) (Fixing FCREPO-841: Add code to determine Fedora resource identifier (object, datastream) from hierarchical resource path) Nevertheless it is curious that the Map returned by relationshipResolver.getRelationships() never even returns the OwnerID. Does this mean it needs changes in the APIM? Any insight on how this was fixed for later versions? (if it ever was?) -- View this message in context: http://fedora-commons.1317035.n2.nabble.com/FeSL-policies-resource-OwnerID-tp7136520p7290657.html Sent from the Fedora Commons Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Fedora-commons-users mailing list Fedora-commons-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
