EPrints Technical Mailing List Archive

See the EPrints wiki for instructions on how to join this mailing list and related information.

Message: #08187

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

Re: [EP-tech] EPrints 3.4.2 release

Hi!
 is there an updated/changes on migration guide from 3.3 to 3.4? Is this the latest: 

https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.eprints.org%2Fw%2FUpgrading_3.3.12%252B_to_3.4&amp;data=01%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cb9d4d79d136447679ee408d8078f2e2a%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=pzR8sbOLvx81Uf8p9SnSL5UcsUZ7gsIrr4OENXS7JCY%3D&amp;reserved=0

?

Il 02/06/20 23:35, David R Newman via Eprints-tech ha scritto:

Hi all,

Work has being ongoing for a new release of EPrints 3.4 (namely 3.4.2)
for a while.  There are several significant features planned for this
new release:

- Capability for enabling caching of citations to improve, particularly
browse view, page load times.

- Improved Accessibility for public front-facing pages (publication
abstract pages, browse views, searches and static content pages such as
the homepage).  As well as a template Accessibility statement page and
report.

- HTTP PATCH functionality to support third-party (particularly
Symplectic Repository Tools 2) to perform incremental metadata changes.

- Support for embedding HTML5 video blocks including subtitles.

- Support for file rather than database stored access records for use in
statistics generation (still somewhat experimental and not enabled by
default).

- A new DOI import plugin using the richer UNIXREF data source.

- New MetaFields for case insensitive IDs (useful for email addresses
and usernames) and keywords, which are backwards compatible (without
database changes) with existing fields used for such metadata.

Along with these there are a number of security and general improvements
along with bug fixes.  More details on these can be found at
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.eprints.org%2Fw%2FEPrints_3.4.2&amp;data=01%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cb9d4d79d136447679ee408d8078f2e2a%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=cKnLz7DvoOoVpmtfHt8usmFCsPC8m%2BcAy3eLVWAhQ%2Fo%3D&amp;reserved=0

A release candidate for EPrints 3.4.2 can be found at
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Feprints%2Feprints3.4%2Freleases%2Ftag%2F3.4.2-rc1&amp;data=01%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cb9d4d79d136447679ee408d8078f2e2a%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=CxnEKdlzl54L6ITMcyfe5SbJNGq2qyxeJf4KqqaBILk%3D&amp;reserved=0

The intention is to make a prodiction release of EPrints 3.4.2 by the
end of the month.  There is also a plan to make a further release of
EPrints by the end of the year.  This will be addressing the outstanding
items in the Accessibility roadmap for EPrints -
https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Faccessibility.eprints-hosting.org%2Faccessibility%2Froadmap.html&amp;data=01%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cb9d4d79d136447679ee408d8078f2e2a%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=zQsY6If6Ij92DhVpCP3jGocKPgBCiMyHwco5omQEtnw%3D&amp;reserved=0

If there are any outstanding bugs that any of you are aware of for
EPrints 3.4 that do not look to be addressed based on the provisional
release notes at https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.eprints.org%2Fw%2FEPrints_3.4.2&amp;data=01%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cb9d4d79d136447679ee408d8078f2e2a%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=cKnLz7DvoOoVpmtfHt8usmFCsPC8m%2BcAy3eLVWAhQ%2Fo%3D&amp;reserved=0 then please
feel free to add an issue to GitHub at
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Feprints%2Feprints3.4%2Fissues&amp;data=01%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cb9d4d79d136447679ee408d8078f2e2a%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=%2FpntIRj3QLNFHVUQzJrhDI1x7HTY8rnHF7bC3xVIZ3s%3D&amp;reserved=0 I cannot guarantee it will
necessarily be addressed for the forthcoming 3.4.2 release but if
practical should be added to a later release milestone.

Regards

David Newman