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

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

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

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

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