Title: Message Title
|
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Richard Rodgers
|
|
Components:
|
DSpace API
|
|
Created:
|
04/Dec/13 11:17 PM
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Tim Donohue
|
|
As reported in DS-1481, because of how DSpace had previously auto-assigned "dc.date.issued" in some scenarios, Google Scholar has reported seeing inaccurate "dc.date.issued" values on many DSpace sites.
Changes to DSpace in 4.0 (linked to DS-1481) should now ensure that DSpace reports a more accurate dc.date.issued (no matter how the content is added to the system).
However, we still need a way to help individual DSpace sites to locate any existing, possibly inaccurate "dc.date.issued" values. It seems like the best way to identify these questionable issued dates is to look for Items where "dc.date.issued=dc.date.accessioned", as those represent items where the issued date was auto-assigned by DSpace (to the date the Item was submitted to DSpace).
Richard Rodgers has begun work on a Curation Task (which can be executed site wide or on specific Communities/collections) which can locate any Items where 'dc.date.issued=dc.date.accessioned' and generate a CSV (suitable for bulk metadata editing import). It's untested, but work has begun at:
https://github.com/richardrodgers/ctask/blob/master/general/src/main/java/org/dspace/ctask/general/RoboIssueDate.java
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
