Re: [Dspace-tech] Creative commons in edit item tool

Mon, 21 Jan 2013 13:02:15 -0800

Hi,

On 22/01/13 09:46, Richard Rodgers wrote:
Just to add to this thread, I think the best approach is to directly edit these related CC fields (or add/remove bitstreams) as seldom as possible,
since it is too easy to introduce inconsistencies among them (e.g. the name doesn't match the URI, or the bitstream, etc).

I agree -- and I think helix and Bram were just looking for a workaround they could use "right now".

To address this need in a 'safer' way, I just put up some curation task code:

that does the following: it uses the license URI as the 'key' and then fetches the values (license Name, and license RDF) from CC and assigns
them to the item. That way one can be assured of having a consistent set of values (2 metadata fields and a bitstream).

Great, thanks for sharing! I have one that kindof does the reverse -- it sets the metadata based on the license RDF: https://github.com/lconz-irr/Curation-Tasks/blob/master/src/main/java/nz/ac/lconz/irr/curate/task/AddCCMetadata.java (I ran this as a one-off over my one repository that uses CC licensing and it worked there, but it hasn't been tested extensively)

cheers,
Andrea

-- 
Dr Andrea Schweer
IRR Technical Specialist, ITS Information Systems
The University of Waikato, Hamilton, New Zealand



------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412
_______________________________________________
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

Reply via email to