2019-11-08 End of Sprint Release

• Added new tenants: KAUST, NCSU, and Victoria
• Ensure that emails from journals will not move datasets out of curation or a published state.
• Fixed problems with multiple deletion requests to Merritt for same files and required manual fixes.
• Removing file paths from the database and codebase to prevent incorrect paths because of symlinks.
• Optimizations to handle load better in Passenger and added a manual script to deal with Passenger memory leaks, as needed.
• Remove non-working sitemap route and modified error notification for known errors that do not indicate application problems.

End of sprint 2019-10-22

• Added new language to describe embargoes when the embargo is dependent on the publication of an article. The new language appears both on dataset landing pages and in confirmation emails to submitters.
• Changed the internal logic for sending emails to users and journals, making it more consistent.
• Updated workflow for items in peer_review status, so curators can edit them and they will remain in peer_review status until they are explicitly moved to a different status.
• Added database content to stash_engine_identifiers.invoice_id, to guarantee that new invoices will not be created for items which had been published into “publicationBlackout” in the old Dryad system.
• Updated internal logic for invoicing to guard against duplicate invoices being created by quick actions in multiple browser tabs.
• Changed streaming method of files to prevent timeouts or premature end of files for users with slower internet connections.
  • Using rack-hijack method to stream instead of controller and each.
  • Streaming into temporary file and separately out of the same temporary file until download is done to prevent issues caused by passenger internal architecture and buffering.
  • Removing temporary files when download completes.

2019-10-22 End of sprint release

v0.4.09

2019-10-22 End of Sprint

2019-10-09: End of sprint

Release Notes

Curation versioning and workflow changes

• Dataset view state for both metadata view and file view/download can be explicitly set per version
• Visibility methods/scopes updated to use explicit display flags & tests updated
• Script for populating view information for versions
• Version visibility is updated upon embargo/publication
• Versions without file changes between subsequent publications do not show as additional versions in the files list
• The entire dataset tracks current overall publishing state (unpublished, embargoed, published, withdrawn)
• Added warning banner for privileged users (owner/admin) who are seeing other than public view
• Allow display of unpublished metadata and additional file versions since publication (or since created) for privileged users
• Privileged users see the sharing link so they can copy and paste it
• Each version displays the internal publication_date set in the database
• Data paper PDF generation is set to show banner (for privileged user preview), files and metadata and data to be consistent with landing page

Stripe invoicing and payment

• Updated Stripe connection so invoices are emailed to users, rather than just being finalized in place
• Added database content to stash_engine_identifiers.invoice_id, with values of “classic-dryad:country” and “classic-dryad:voucher” to indicate items that were exempted from payment in Classic Dryad
• Extended API of the journal module (in Classic Dryad) that reports the email addresses to be notified when a dataset is approved for publication
• Added functionality to use the above API change. When a dataset is set to “published” or “embargoed”, if the dataset has not been previously published, an email is sent to the email addresses for the associated journal

General UI changes

• Added a “Preview” link to the user dashboard so users have a more obvious method to view previously-submitted datasets

Sharing links for dataset rather than for each version

• Sharing links are migrated and re-associated with the dataset rather than version
  • References to sharing links are updated in code so all is working
  • Code cleanup for dead code no longer used for sharing links
  • Automated testing added for new sharing links

Infrastructure and non-user-facing tasks

• No longer forcing SSL in the application. Application Load Balancer does that and allows Nagios tests to run directly against the application workers (they will not run over SSL or it makes it much more difficult, it seems)
• Capybara browser testing fixed to eliminate randomly failing test suite because of testing order
• Testing added to exercise changed/added functionality at unit and feature (or requests) tests level

v0.3.18

Added web mock for ROR heartbeat