Mark, On 5/18/2012 12:58 PM, Mark Diggory wrote: > > Right now, I'm just looking for > > 1.) Where to add Date Ranges to your existing ResourcePolicies encoded > in Rights.
As I mentioned, currently date ranges cannot be stored in METSRights (it's a limitation of the schema) -- that's why this discussion led elsewhere (into PREMIS and similar). So, we'd either have to create a new custom DSpace rights schema, or look for something else that meets our needs. The only other option is to continue to store Embargo date ranges in metadata fields, which works fine in DSpace 1.8.x (and can be exported and restored via AIPs) > 2.) Where to add any "Name" or "Description" encoded in the proposed new > ResourcePolicy fields that will describe the purpose of the ResourcePolicy. Digging around in METSRights, I'm not exactly sure where this would go either. So, it may be that we are "out-growing" METSRights schema, and we need to migrate to something new for AIPs. Again, METSRights was chosen because it could accurately describe the existing ResourcePolicies. But, if you are changing how ResourcePolicies act/function, then METSRights may no longer be accurate enough to describe these new types of ResoucePolicies. - Tim ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
