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

Review "time travel" #172

Open
fossygirl opened this issue Jun 20, 2018 · 3 comments
Open

Review "time travel" #172

fossygirl opened this issue Jun 20, 2018 · 3 comments

Comments

@fossygirl
Copy link
Member

Given the ability to contribute changes to data, users should also have the ability to go back and see the data for a definition at other points in time. All views of a component should indicate whether or not there have been merged contributions (curations) and whether or not there are pending contributions. Users should be able to select from the past, current and pending states of the definition and view them in full fidelity across all the levels of detail.

@storrisi
Copy link
Contributor

I think it could be considered related to showing all the curations details.
When the expanded=prs behavior would start to return some data, we'll be able to show all the required details.
At that time we'll should see if some other details are needed to solve this particular requirement.

@storrisi
Copy link
Contributor

We should check if what has been done in #515 will meet the requirement of this issue, or other work is required.

@dabutvin
Copy link
Member

I think this is one step further.
While we can see the information about past curations now, this is asking to be able to load an older version of a component.

We might have to start storing definition history instead of always overwriting them to pull this off

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

No branches or pull requests

4 participants