Page History
...
- DSpace 4.0 Status. Release Candidate 1 planning (Thu, Oct 31).
- might warrant a brief discussion and approval: https://github.com/DSpace/DSpace/pull/363
got left behind and is marked as an improvement, not a bug. Shall we do anything about it for 4.0?Jira server DuraSpace JIRA key DS-1481 - Tim received an email update from Google Scholar team lead over the weekend. This DS-1481 issue seems to be even more widespread than thought (they are seeing date metadata issues in many/most DSpace instances). They'd really like us to resolve this in 4.0 if we can.
- Google says the problem seems to be that DSpace reports a recent "dc.date.issued" (2011, 2012, 2013, etc.) but Google Scholar has found a much older date in the PDF/Word document (e.g. 1960, 1987), or via other sources (e.g. cross-checking publisher sites, etc). This causes issues in Google Scholar when attempting to do a search by date, as DSpace items may show up under an incorrect dates.
- DSpace 4.0 Tasks
- I updated the New features section of Release Notes. Please, check your contributions, add descriptions, credits, images etc. --Ivan
- TODO: Send an announcement (to all lists) of the upcoming 4.0 features & upcoming testathon. Help to generate some excitement!
- Search Interfaces (possibly standardizing on Discovery as the interface, with multiple providers)
- In DSpace 4.0, Discovery is enabled by default
- What do we want to do about plain-Lucene support?
- Option 1: Deprecate it in 4.0, and remove entirely in 5.0
- Option 2: Rewrite it so that it can be another provider behind Discovery (alongside Solr and possibly ES)
- For 5.0, we could also tentatively plan to release a Discovery on Elastic Search option
...
Overview
Content Tools