Title: Message Title
|
|
|
|
It's going to have to be configurable, it seems. We have two incompatible cases:
a) Most submissions are published by submission to this DSpace. dc.date.issued = dc.date.accessioned makes sense and should be the default.
b) Most submissions are of works previously published or soon to be published elsewhere. If dc.date.issued = dc.date.accessioned, it is probably wrong.
People use DSpace both ways. We need a way to say which way this instance is used. Possibly, which way this Collection is used. The way to know which treatment is correct, is for the people running the instance to tell it.
|
|
|
|
|
|
|
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 a...
|
|
|
|
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
