[
https://jira.duraspace.org/browse/DS-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27675#comment-27675
]
Tim Donohue commented on DS-1481:
---------------------------------
One other brainstorm...
Perhaps if you explicitly say "dc.date.issued = 'today'" (i.e. literally set it
to the string "today"), the DSpace will know to transform that into today's
date. That way you could pass this value in via SWORD, LNI, any UI, etc. It
might be a way to ensure the IR manager need not do too much heavily lifting,
while also making it explicit to DSpace whether this item should have an empty
"dc.date.issued" or a "dc.date.issued = dc.date.accessioned"
The idea of Collection validators is also interesting, I admit.
In any case, I agree, this needs some thought. Good to hear though that we all
see the problem -- just a matter of coming up with a reasonable solution.
> "dc.date.issued" is often incorrectly set (reported from Google)
> ----------------------------------------------------------------
>
> Key: DS-1481
> URL: https://jira.duraspace.org/browse/DS-1481
> Project: DSpace
> Issue Type: Improvement
> Components: DSpace API
> Affects Versions: 1.7.0, 1.7.1, 1.7.2, 1.8.0, 1.8.1, 1.8.2, 3.0, 3.1
> Reporter: Tim Donohue
> Fix For: 4.0
>
>
> Google (Anurag Acharya and Darcy Darpa) has contacted DuraSpace about a
> common indexing issue affecting all DSpace sites.
> When Google & Google Scholar index DSpace content (from a variety of
> institutions), the "dc.date.issued" value is incorrect the majority of the
> time. The reason is that, if unspecified, DSpace sets this issued date to the
> *date of accession* (i.e. date that it was submitted to DSpace), see:
> https://github.com/DSpace/DSpace/blob/master/dspace-api/src/main/java/org/dspace/content/InstallItem.java#L130
> Google says this causes their crawlers (for both Google & Google Scholar) to
> assume that the date of accession is actually the formal publication date.
> Rather than defaulting the 'dc.date.issued' to the accession date, Google
> recommends we leave it blank. DSpace is already tracking the accession date
> separately (in 'dc.date.accessioned'), so it seems odd to set
> 'dc.date.issued' to the same value by default.
> Google will be sending along some examples of this. They said they have seen
> repositories, where 30-50% of their items all have the same "dc.date.issued",
> as those items were all imported on the same date.
> This seems like a very reasonable recommendation to me as well. I'm not sure
> we should be setting 'dc.date.issued' by default, as it really is meant to be
> the date of *formal publication*, and not the date that something is made
> available on the web.
> This also seems like a small fix (remove a few lines from InstallItem).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
