#X MIRAGE REGISTRATION CODE UPDATE#
#X MIRAGE REGISTRATION CODE DRIVER#
#X MIRAGE REGISTRATION CODE UPGRADE#
#X MIRAGE REGISTRATION CODE PASSWORD#

#X MIRAGE REGISTRATION CODE UPDATE#

Update Mirage to use recommended MathJax inline delimitersВ ( DS-3087)В and to use new CDN location ( DS-3560).

Fixed bitstream download issues which could leave AWS connections open when using S3 storage backend: DS-3870.

Fix issue where search results lose Community/Collection context when sorting: DS-3835.

Fixed Unicode character issues in metadata: DS-3733.

Fixed occasional Hibernate LazyInitializationException when completing submissions: DS-3775.

Fixed performance issues for Items with 100+ bitstreams: DS-3883.

Fixed Mirage v2 build issues caused by Bower Registry URL change: DS-3936.

Fixed issues with pausing HTML5 uploads: DS-3865.

Fixed issues with authority control popup: DS-3404.

Cleanup EHCache configuration: DS-3694В and DS-3710.

Fix PubMed Import submission step ( StartSubmissionLookupStep) to use updated URL of PubMed API: DS-3933.

Fix MediaFilter 'too many open files' issues (where it forgot to close an input stream): DS-3700.

Ensure ImageMagick thumbnailsВ respect the orientation of original file: DS-3839.

Update last modified timestamp (on Item) when a new bitstream is added: DS-3734.

Fixed issues with Solr Search Query escaping in both UIs: DS-3507.

#X MIRAGE REGISTRATION CODE PASSWORD#

Fixed issue where Shibboleth authentication plugin appeared to login when no password provided: DS-3662.

Fixed issues where Item Level VersioningВ accidentally duplicated both metadata ( DS-3703) and bitstreams ( DS-3702).

Other API-level fixes (affecting all UIs).

Note: This issue was limited to 6.0, 6.1 or 6.2, and specifically ONLY occurred when Item Level VersioningВ was first enabled on DSpace version 4.x or 5.x (and that old versioning data had since been migrated to 6.x).

Fixed issues where Bitstreams were removed from all versions of an ItemВ (resulting in inaccurate versioning) when deleted from the latest version of an Item: DS-3627.

Note: This issue was limited to 6.0, 6.1 or 6.2, and specifically occurred when Item Level VersioningВ was NOT enabled (which is the default setting) or when Item Level Versioning was first enabled on DSpace version 6.0, 6.1 or 6.2.

Fixed issues where Bitstreams were not being removed from assetstore even when flagged as deleted: DS-3627В and DS-3461.

Fixed issues where Bitstreams were not being flagged for deletion when an Item was deleted: DS-3729.

Bitstream deletion issues ('dspace cleanup' command).

Fix issue where DSpace wasn't starting if it used a database connection pool supplied through JNDI: DS-3434.

#X MIRAGE REGISTRATION CODE DRIVER#

PostgreSQL JDBC driver upgraded to latest version (to allow for full compatibility with PostgreSQL v10): DS-3854.

Configurable Workflow migration threw errors: DS-3788

Update DSpace StatisticsВ to use GeoIP API v2 (instead of now discontinued GeoIP API v1): DS-3832.Update DSpace ORCID IntegrationВ to use ORCID API v2 (instead of now obsolete ORCID v1): DS-3447.Reported by Eike Kleiner (ZHAW, Zurich University of Applied Sciences) Additionally, the exported CSV included metadata fields which are flagged as hidden in configuration.В ( В - requires a JIRA account to access.)

Any user was able to export metadata to CSV format if they knew the correct JSPUI path/parameters. This is most severe in sites which allow anyone to register for a new account.В ( В - requires a JIRA account to access.) A user can inject malicious Javascript into the names of EPeople or Groups. One configuration addition ( В property) has been made to the default dspace.cfg to support the new ORCID API v2, for ORCID Authority Control users. No database changes should be necessary when upgrading from DSpace 6.x to 6.3.

#X MIRAGE REGISTRATION CODE UPGRADE#

As it only provides only bug fixes, DSpace 6.3 should constitute an easy upgrade from DSpace 6.x for most users. To ensure your 6.x JSPUI site is secure, we highly recommend ALL JSPUI DSpace 6.x users upgrade to DSpace 6.3ДSpace 6.x XMLUI users may also wish to upgrade as several major bugs have been fixed in the XMLUI as well.ДSpace 6.3 upgrade instructions are available at: Upgrading DSpaceДSpace 6.3 is a bug fix releaseВ to resolve several issues located in previous 6.x releases. DSpace 6.3 contains security fixes for the JSPUI (only).

X mirage registration code