Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document a Riprap schema #4

Open
mjordan opened this issue Oct 2, 2018 · 3 comments
Open

Document a Riprap schema #4

mjordan opened this issue Oct 2, 2018 · 3 comments
Assignees

Comments

@mjordan
Copy link
Owner

mjordan commented Oct 2, 2018

This would basically describe the database structure, but would be framed such that any plugin needs to persist data in its own way corresponding to this schema.

@mjordan mjordan self-assigned this Oct 3, 2018
@mjordan
Copy link
Owner Author

mjordan commented Oct 3, 2018

datestamp has a string value, for the following reasons:

  • in the PREMIS 3.0 schema, it has a string data type and not a date/time data type
  • if we use ISO 8601, the timezone is encoded in the string
  • strings are much more storage-agnostic than date data types.

The value must account for Daylight Saving Time.

@mjordan
Copy link
Owner Author

mjordan commented Oct 3, 2018

The schema should use elements that are consistent with the command options:

Plus:

  • event_detail
  • event_outcome_detail_note

mjordan added a commit that referenced this issue Jan 4, 2019
@mjordan
Copy link
Owner Author

mjordan commented Jan 4, 2019

The database structure should be described as part of persist plugin documentation. WIP in branch issue-26.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant