search

edgeryders / discourse-annotator

A text annotation and analysis application for Discourse. Made with Annotator.js and Ruby on Rails.
https://edgeryders.eu/t/6811
Other
4 stars 0 forks source link

Keeping track of code histories #208

Open albertocottica opened 3 years ago

albertocottica commented 3 years ago

Ethnographers do a lot of work with rationalizing their codes ontology: splitting, merging, renaming etc.

Is there a way to keep track of these changes, like a revision history?

tanius commented 3 years ago

Currently, the history of changes to ethnographic codes is not recorded. If this is a feature that users want, we can add it during one of our projects, as there will be budget for maintenance of this software.

However, due to the multilingual code names there is a lot of complexity in data structures already, and planned future improvements to keep track with revisions to coded texts (rather than codes) would only add to that complexity. So if at all, I propose that this feature would take the form of a revision log, not of an undo/redo history. The difference is, there is no direct support for restoring a revision in a log, just information about what was changed in what order. It is straightforward to implement and does not add to data structure complexity, since it would live in its own log table in the database.

albertocottica commented 3 years ago

Thanks.

If this is a feature that users want, we can add it during one of our projects, as there will be budget for maintenance of this software.

Do you mean future or extant projects?

tanius commented 3 years ago

There's no IT budget left in the currently running projects, except a bit for security maintenance and emergencies. But the feature can be implemented as part of the Treasure project.

albertocottica commented 3 years ago

Noted with thanks. Let's set aside this issue for a further milestone.