UX: "not latest version"– how do I find the latest?

[Frijol]

There's a helpful "not latest version" tag on a dataset I'm viewing in the app:

It's blue, but not a link. How do I use it to get the latest version? (Can I see all the versions in a list somewhere? Is there any automated diffing between versions?)

[ramfox]

Is this on the app.qri.io page?

Can you let me know what dataset you were looking at so i can recreate?

Thanks :)

[ramfox]

I'm only seeing this when you got to "history" and click on a previous version (which is intended)
You can get to the latest version by going back into history, and clicking the most recent version.

Although perhaps it would be good to have it be a link and rather than say "not latest version" say "go to latest version" that sends you to that latest.

Alternatively, I could just change from blue to grey (since you are right, on the app links are blue), so we aren't violating our "links are blue" principle, and assume folks will know that to get to the most recent version they can just look at the most recent thing in the history?

[Frijol]

This one is in the app, actually! It's on /b5/texas_tceq_lynchburg_ferry_auto_gc/at/ipfs/QmZPbRDKRM3sKqdybZPYmPacUT56JFq1BAaSuUhvCqpNHd

I think I wholly don't know how to interface with the "history" section– I know this particular dataset has been updating daily, but I don't know how to see several versions of it.

[Frijol]

I got to this URL by copying from an app.qri.io url I was sent

[ramfox]

Ooooooo thank you for the details. I think I understand what's going on.

This is interesting and there is currently no documentation on this:
Qri won't auto-pull updates on a dataset that isn't yours. So if you have added someone else's dataset, and you want the updates, right now, you have to go on the registry and to add the new version yourself.

This may be difficult for you right now, because I recently shipped some fixes that help our pagination. We are releasing an update to the frontend today or tomorrow that has these fixes. There are also some backend qri add fixes that need to land for this workflow to work properly, also landing today or tomorrow.

What really should happen is you should be able to say "Check this for updates every day and give me all the updates that have happened since the last time I looked", that way the data is always fresh. This is different than the update functionality that we have in the backend already: those updates update your own dataset, this one should pull updates that others have run and add them to your repo.

We can mimic this using qri update to run a shell script that just calls qri add <peername>/<datasetname> periodically.

This is a workflow that a lot of people will want, we need to think through it. Tagging @b5 for thoughts