Skip to content

releasenotes.md

Latest commit

 

History

History
158 lines (114 loc) · 5.89 KB

releasenotes.md

File metadata and controls

158 lines (114 loc) · 5.89 KB

Fix 2025-04-24

There is a user without name! I supplied a name based on the email address, checked the code, tried to prevent it in the future, and added guards to prevent such users from modifying data.

Release 1.1.0 on 2025-04-07

There were lots of conflicts between delete actions and other actions that accessed the same data during deletion. The disk with temporary files filled up. This called for a different deletion strategy: instead of physically deleting stuff, we mark it as deleted. The other ingredient of this strategy is a sweeper: a process that periodically checks which items have been deleted more than 31 days ago, and then permanently deletes those items. Until that time, admins can restore them.

There was also a misleading button on the edition page: Delete scene. Instead of deleting the scen file, it deleted the whole edition.

That has caused some editions to be lost, but we could retrieve them again from the backups. They have been restored.

The system generates more complete logging information on critical actions such as delete, download, and upload, so that future issues can be inspected more easily.

Now that the MyWork page for admin gets crammed with sections, we provide a table of contents on the right hand side of the page.

Fix 2025-01-20

Somehow the assignment of roles to users with respect to an edition or project was broken. It has been fixed.

Release 1.1.0 2025-01-16

There was a blocking issue (Internal Server Error) having to do with titles with a : in it: those were interpreted as a dictionary instead of a string.

Fixed by preventing that yaml metadata fields are interpreted as dicts. Only strings and lists of strings are allowed.

There was also an issue with the display of the fields funder and audience on the published pages. This was caused by the fact that the template assumed these had lists of values in it, whereas the page generator produced them as single string markdown fields. Fixed by leaving the template intact, but declaring the fields as (multiple) strings.

Release 2024-12-09

There were issues with downloading projects and editions, especially when they were large.

  1. An out-of-memory error. This was caused because the app created the zip files for download in memory.

    Fix: the zipfile is now created in a temporary directory.

  2. The app sent the download in one massive body.

    Fix: the zipfile is now streamed to the client.

  3. The request timed out, because zipping took too long.

    Fix: when we add files to the zip file, we do not compress glb, mp4 files etc. This reduces the zipping time greatly.

  4. The download fails near the end. So: the request succeeds, the server sends the response, but in the end the client reports that the server has dropped the connection.

    Fix: not known yet. Instead, downloads of projects/editions whose unzipped size exceeds 1 GB are prevented, and the user will get a warning about that.

  5. The maximum upload size is currently 500 MB.

Fix 2024-12-10

Improvements in metadata handling and visual design.

This involved quite a number of under-the-hood actions, which are reported in the internal pure3d repo.

Release 2024-11-18

In this release we have changed the metadata schema.

The field dc.instructionalMethod has been removed.

Several dc (or pseudo dc) fields have been added, resulting in:

  • title (existing)
  • subtitle (new)
  • creator (existing)
  • contributor (existing) Voyager related data such as model, scene, articles, media)
  • datePublished (date of last publishing, also present if an edition has been unpublished)
  • dateUnPublished (date of last un-publishing, also present if an edition has been re-published)
  • dateCreated (registers the creation date of projects and editions)
  • dateModified (registers the time of last modification to the metadata, not to the
  • abstract (existing)
  • description (existing)
  • rights.license (new)
  • rights.holder (new)
  • contact (new)
  • keyword (new, values filled from previous subject)
  • audience (new, controlled vocab)
  • funder (new)
  • coverage.country (new, controlled vocab)
  • coverage.geo (new, free text meant for latitude-longitude)
  • coverage.place (unchanged, free text meant for latitude-longitude)
  • coverage.period (existing, but now with controlled vocab)
  • coverage.temporal (existing, but now with free text)
  • subject (existing, with new contents, controlled vocab)
  • language (new, controlled vocab)
  • source (new, controlled vocab)
  • provenance (existing)

All these fields are valid for editions. For projects only the following fields are valid:

  • title
  • subtitle
  • creator
  • contributor
  • dateCreated
  • dateModified
  • abstract
  • description

All date fields will be filled in by the system if the corresponding action occurs.

In order to get the metadata right for published editions, every published edition must undergo the following actions:

  1. unpublish the edition;
  2. check and correct the metadata;
  3. republish the edition (if there are warnings/errors that can not be resolved, you may force-republish the edition.

After having treated all published editions this way, have a look at the projects that you want to feature, and put their publication number in the Featured Published Projects, using the control on the MyWork page under Published Project.

Then click the button Regenerate Pages under the featured pages to make the choice effective.

Fix 2024-05-19

Moved location for temp files off the data volume to a new temp volume, which is excluded from backup.

Release 1.0.0 2024-05-16

Pure3D went in production.
⚡