A recent submission (mds2-2225) highlighted some problems with the display versions on the landing page:
Sometimes, the message about a newer version available would erroneously appear; this is apparently due to an error in sorting versions.
Links to previous versions really only resolved to the latest version.
This is the subject of ODD-910 which is addressed in this PR.
This problem has been addressed in a somewhat temporary way:
The message about a newer version is suppressed when the it relies on version sorting; It will still appear if the record has a "isReplacedBy" property (which is still relevant in a few cases).
Links to previous versions in the Version History listing have been removed, unless they point to a record with a different identifier.
To test under oar-docker, it is recommended that you load a particular record that demonstrates the problem being fixed (process described below). Further, it is recommended to to first run oar-docker without the fix. In detail, do the following:
Build and start locally a 1.4 version of oar-docker/apps without updating the deployment.yml file (i.e. use either the current integration or main branch).
Copy the test record from the oar-pdr PR branch, angular/src/assets/mds2-2225.json, to your current directory so that you can load it.
A recent submission (mds2-2225) highlighted some problems with the display versions on the landing page:
This is the subject of ODD-910 which is addressed in this PR.
This problem has been addressed in a somewhat temporary way:
To test under oar-docker, it is recommended that you load a particular record that demonstrates the problem being fixed (process described below). Further, it is recommended to to first run oar-docker without the fix. In detail, do the following:
Build and start locally a 1.4 version of oar-docker/apps without updating the
deployment.ymlfile (i.e. use either the currentintegrationormainbranch).Copy the test record from the oar-pdr PR branch,
angular/src/assets/mds2-2225.json, to your current directory so that you can load it.Load. record with this curl command:
This should return status 201 (Accepted).
Access the landing page via https://localhost/od/id/mds2-2225
Note the problems:
Now stop the
appsapp, edit thedeployment.ymlfile to use this PR branch, rebuild, and run.Reload the landing page for mds2-2225. (You should not need to reload the record via curl.)
Note the correction of problems: