[Dspace-tech] (no subject)

2012-12-27 Thread Peter Dietz
Hi All,

I was wondering if I could get some feedback from people who have been
using Creative-Commons licensing before-and-after DSpace 1.8 (when the REST
API licensing rewrite was added to DSpace).

In 1.7 and below, when viewing an Item, it looks for a bitstream in the
CC-LICENSE bundle, and tries to grad the URI from the appropriate
bitstream, upon page load.

In 1.8 and later, when viewing an Item, the license metadata gets added to
a CC-Name and a CC-URI metadata field. The UI just points to those metadata
fields to indicate the proper license.

This leaves one with a legacy problem, as mentioned in the 1.8 release
notes.


DS-964 https://jira.duraspace.org/browse/DS-964 Rewrite of Creative
Commons 
licensinghttps://wiki.duraspace.org/display/DSDOC18/Configuration#Configuration-ConfiguringCreativeCommonsLicense
for
XMLUI

   - Better integrates the Creative Commons licence selection into the
   submission process
   - Legacy problem – do we update old license to new or not? Currently MIT
   runs 'split version' with old licenses looking like old, and new look like
   new.
   Provided by MIT.



So, we have just started to roll out our upgrade to 1.8 locally, (we're a
little late to the party), and we're not happy with being stuck with a
legacy problem. So I was wondering if anyone has done anything to their
items to address this situation.

For us, we've built a Curation-Task to migrate the old Items with
CC-License to fill in their CC-Name and CC-URI metadata fields.

You can take a look at the code for it if you are interested.

https://github.com/osulibraries/DSpace/blob/osukb/dspace-api/src/main/java/org/dspace/ctask/general/CreativeCommonsMetadataMigration.java

It essentially gets ran once during the upgrade, goes through all Items in
your repository with a CC-LICENSE bitstream, extracts the LICENSE-URI from
a bitstream, compares that with a locally maintained table of license
options, and fills in CC-NAME and CC-URI metadata fields. (We've chosen
dc.rights.cc and dc.rights.ccuri). I've run into performance issues on
running a curation task recursively over the entire site-level, and had to
make some optimizations to the distribute method, but it runs pretty well
now.

Peter Dietz
--
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. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122712___
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

Re: [Dspace-tech] (no subject)

2012-12-27 Thread Richard Rodgers
Hi Peter:

This looks great and we'll have a closer look, since we are likewise in a 1.8 
local upgrade process and would like to 'normalize' the CC License 
representations.

A few cursory observations in the meantime:

I see the task sets the metadata fields, but does not delete the (now 
presumably unneeded) CC bitstreams. They are tiny, but I suppose there is a 
remote possibility that the metadata field and the bitstream could come to 
differ, and there would be some head-scratching.

I like the optimization for running over entire sites. In fact, more recent  
curation work has generalized your approach so that any task can be run against 
a DB-query (or index search):

see

https://github.com/richardrodgers/mds/blob/master/kernel/src/main/java/org/dspace/curate/ObjectSelector.java

and

https://github.com/richardrodgers/mds/blob/master/kernel/src/main/java/org/dspace/curate/selector/QuerySelector.java

Thanks again,

Richard R

On Dec 27, 2012, at 2:22 PM, Peter Dietz wrote:

Hi All,

I was wondering if I could get some feedback from people who have been using 
Creative-Commons licensing before-and-after DSpace 1.8 (when the REST API 
licensing rewrite was added to DSpace).

In 1.7 and below, when viewing an Item, it looks for a bitstream in the 
CC-LICENSE bundle, and tries to grad the URI from the appropriate bitstream, 
upon page load.

In 1.8 and later, when viewing an Item, the license metadata gets added to a 
CC-Name and a CC-URI metadata field. The UI just points to those metadata 
fields to indicate the proper license.

This leaves one with a legacy problem, as mentioned in the 1.8 release notes.



DS-964https://jira.duraspace.org/browse/DS-964 Rewrite of Creative Commons 
licensinghttps://wiki.duraspace.org/display/DSDOC18/Configuration#Configuration-ConfiguringCreativeCommonsLicense
 for XMLUI

  *   Better integrates the Creative Commons licence selection into the 
submission process
  *   Legacy problem – do we update old license to new or not? Currently MIT 
runs 'split version' with old licenses looking like old, and new look like new.
Provided by MIT.



So, we have just started to roll out our upgrade to 1.8 locally, (we're a 
little late to the party), and we're not happy with being stuck with a legacy 
problem. So I was wondering if anyone has done anything to their items to 
address this situation.

For us, we've built a Curation-Task to migrate the old Items with CC-License to 
fill in their CC-Name and CC-URI metadata fields.

You can take a look at the code for it if you are interested.

https://github.com/osulibraries/DSpace/blob/osukb/dspace-api/src/main/java/org/dspace/ctask/general/CreativeCommonsMetadataMigration.java

It essentially gets ran once during the upgrade, goes through all Items in your 
repository with a CC-LICENSE bitstream, extracts the LICENSE-URI from a 
bitstream, compares that with a locally maintained table of license options, 
and fills in CC-NAME and CC-URI metadata fields. (We've chosen 
dc.rights.cchttp://dc.rights.cc/ and dc.rights.ccuri). I've run into 
performance issues on running a curation task recursively over the entire 
site-level, and had to make some optimizations to the distribute method, but it 
runs pretty well now.

Peter Dietz
--
Master Visual Studio, SharePoint, SQL, ASP.NEThttp://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. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122712___
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

--
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. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122712___
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

[Dspace-tech] DSpace as an authority control for authors

2012-12-27 Thread Nemiz, Elvi
Dear all,

Previously I used LCName authority plugin to lookup and to make the authors
authority-controlled. I edited some authority keys since it shows up in
sidebar facets and browse by authors pages. If I don't want to use LCName
plugin anymore, and instead want to lookup to existing authors that have
already an authority key, how can I achieve this? Did anybody somehow
modified the existing SampleAuthority plugin to get it to lookup existing
values from the DSpace database? Would it still be possible if I'm
using SolrBrowseDAO in my Browse Configuration instead of the default? I'm
using dspace 3.0, xmlui with discovery enabled.  Thanks in advance.

Regards,
Elvi S. Nemiz
--
Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and
much more. Get web development skills now with LearnDevNow -
350+ hours of 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_122812___
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