TigerData is a comprehensive set of data storage and management tools and services that provides storage capacity, reliability, functionality, and performance to meet the needs of a rapidly changing research landscape and to enable new opportunities for leveraging the power of institutional data.
As a Data Sponsor, when I review my project's details, I need to see event markers for submission requests, along with the current status, so that I can fulfill my duty of project monitoring and decide whether any further action is required.
Notes
We don't have all the details worked out yet for recording provenance in project metadata. The goal with this issue is to make a little progress by having a place to show key details to Data Sponsors on the Project Details page. I don't want this to be a blocker for #287, and it looks like some headway was already made in #264 and #302.
As of Dec. 13, I don't see a provenance section in staging yet:
For new project requests covered by #113, we certainly have a way to record who submitted the request, and presumably we can record a timestamp of when that happened (please, always use the ISO 8601 standard for all dates and times in metadata). When a new project is requested, the first status it receives is always "Pending".
We do not yet have a way to interoperate with other systems to automatically record project request approvals or update statuses from "Pending" to "Active". I suggest the way to keep moving forward in the meantime is to focus only on recording the submission request provenance.
Completion Criteria
[x] Create a rails class called ProvenanceEvent where these will be stored
[x] The ProvenanceEvent has the following Fields:
Event Type [ "Submission", "Status Update" ]
Event Details [ see below criteria for submission ]
Event Person [ netid of the creator ]
Event timestamp [ timestamp on creation ]
[x] The preliminary "Project Details" page includes a section with the heading "Provenance" below the "Automatic Settings" section
[x] The "Provenance" section on the display includes 2 fields (in order): "Submission" and "Status"
Status is the current status
Submission is the list of Event Details for the Request and the Approval only
[x] Submission Event Details: The "Submission" field displays, for now, "Requested by [data sponsor name], [timestamp]", where [data sponsor name] is filled by the full name of the person who submitted the request form for that project and [timestamp] is filled by the ISO 8601-standardized date and time with time zone offset, as recorded by the server at the time of project request submission
[x] Status Event Details: The Status was updated from [original] to [new]
[x] When a Project form is submitted two Provenance Events are created Submission & Status
User Story
As a Data Sponsor, when I review my project's details, I need to see event markers for submission requests, along with the current status, so that I can fulfill my duty of project monitoring and decide whether any further action is required.
Notes
We don't have all the details worked out yet for recording provenance in project metadata. The goal with this issue is to make a little progress by having a place to show key details to Data Sponsors on the Project Details page. I don't want this to be a blocker for #287, and it looks like some headway was already made in #264 and #302.
As of Dec. 13, I don't see a provenance section in staging yet:
For new project requests covered by #113, we certainly have a way to record who submitted the request, and presumably we can record a timestamp of when that happened (please, always use the ISO 8601 standard for all dates and times in metadata). When a new project is requested, the first status it receives is always "Pending".
We do not yet have a way to interoperate with other systems to automatically record project request approvals or update statuses from "Pending" to "Active". I suggest the way to keep moving forward in the meantime is to focus only on recording the submission request provenance.
Completion Criteria