curationexperts / cypripedium Goto Github PK

• location field uses geonames to auto complete
• uses FRBM geonames account

• Make sure default admin set can display and add encoded slashes fix to these servers

One for each work type

• Configure devise password complexity to comply with FRBM requirements

This is the tracking ticket for the migration of the Sargent and Sims collection. This is the first collection we'll work on.

ACCEPTANCE

• Gemfile references specific version of ruby for the project

Looks like we're on Ubuntu 16.10 right now, which is near end of life:

Welcome to Ubuntu 16.10 (GNU/Linux 4.8.0-41-generic x86_64)

• Documentation: https://help.ubuntu.com
• Management: https://landscape.canonical.com
• Support: https://ubuntu.com/advantage

Get cloud support with Ubuntu Advantage Cloud Guest:
http://www.ubuntu.com/business/services/cloud

0 packages can be updated.
0 updates are security updates.

Your Ubuntu release is not supported anymore.
For upgrade information, please visit:
http://www.ubuntu.com/releaseendoflife

New release '17.04' available.
Run 'do-release-upgrade' to upgrade to it.

Maybe add a "touch tmp/restart.txt" post deploy?

It isn't reporting coverage on the README right now

The titles current look like "title / author"

• Drop everything after the last slash

• Create an admin user on the console
• Ensure this is documented

• Users cannot self-register for the application
• Users cannot access the /users/sign_up path

• Be able to go to https://cypripedium.curationexperts.com instead of http://34.227.251.196/

• Specify the name of the collection in the top of the export file in <collection_name>
• For each import file, ensure it's collection exists and add all records to that collection

• currently deployed version of code should appear in page footer

• be able to cap deploy to sandbox server

• Set up SSL
• Everyone should be forced to use SSL and port 443

• All works should have visibility "open"

• Give the user some feedback that the importer is running and how far along it is

STORY
As a repository admin I would like a place to store DOIs in the metadata for a work.

ACCEPTANCE

• There is a DOI field in the edit view that accepts arbitrary string values
• When a DOI has been added to a work, is displays in the show view
• Blank DOIs don't display and empty label

• sample data rake task
• generate a conference proceeding
• generate a data set
• generate a publication

to address security vulnerability

• Ensure ansible build gets all the way through instead of failing on missing production.rb file

• If <work_type> is set, override the work type for an object. E.g., Sargent and Sims will be mostly publications, but there will be a few <work_type>ConferenceProceeding</work_type>

• Use "Quid Pro Quo" staff report 486 as a fixture object
• It should have all the metadata fields of the original
• It should have a few of the binary files of the original

• sidekiq UI mounted at /sidekiq
• access limited to admin users

• The file name of the appropriate PDF should match the value of the identifier element
• if there is no <identifier> element for the record, do not try to attach a PDF

• Remove "paper" work type
• Create "publication" work type

• all built via ansible
• all with capistrano deploy targets
  • qa
  • stage
  • production

• All objects in a collection will become the same kind of Work (e.g., DataSet). Be able to specify the data type at import time

• Derivatives should work on Ubuntu 16.04 LTS for long term support

• create required fields
• finish metadata import mapping

Data here:
https://docs.google.com/spreadsheets/d/1Ms2XaewI4wlEiaYAt9OF8-fpJ-Y4wdWDTj4NwhymNaU/edit#gid=1164960854