Closed KevinThiele closed 8 years ago
This is not in SDD, so it will require a separate web service, as I don't think ALA Keys will support it.
I am not sure if I want it back in the same form, as I would like to explore proper revision history (which is very hard for pathway keys).
So far, it has only been used by a single person.
I am going to put it back for now, by the way, but I'll leave the issue open.
Yes by a single person, but a pretty important person!
The reason why it’s important is that we will increasingly need to manage uploaded keys, and tracking edits becomes important. Other users of KeyBase may well upload a key then just leave it alone, so they would have no use for this. I use it all the time for keeping critical historical information as to howe the key evolves and is edited over time. This will be very important in future, even though for many users it isn’t now.
I think that is in the eyes of the beholder.
My argument is not that revision management is not important, but that this is not the right way to do it.
So what’s the right way?
I think I would like to store the old versions and then do a diff. This should give you the change note without actually having to write it down.
Yes, the problem is that the change note may be more than just a diff – it’s useful sometimes to give a reason for the change, rather than just the bald change itself.
Let's do both then.
The change notes are back. It turned out it was only a typo that kept them out, but now the whole page comes from web services.
The Changes tab under a key's About is no longer working - just gives a list of taxa. This is a useful tab reports changes that have been made to a key since it was uploaded) - please reinstate