Record editing thoughts and ideas

[ngerakines]

Editing records is possible through XRPC calls. What doesn't exist is a standard of meta-data.

Should an edited record:

• Have a timestamp of when it was last changed?
• Link to an old version?
• Have an edited bool?

[bleonard252]

If you mean as a convention, a timestamp should be provided, yes. It would be treated just like existing "created at" timestamps, but, you know, for updated records. I think I'm already doing that for Northwood records. I'm not sure what the scope is but there should be a full list of revision CIDs for a record, at a different XRPC endpoint, which could be used to determine "cold" if it's edited.

The presence of an "updated at" timestamp implies that it's been edited, and if an old version is needed, you'd use that record history endpoint (getRecordHistory? getRecordRevisions?) to get it.

[tom-sherman]

Without a way to view the history I'm not sure how valuable an edited bool or createdAt date is. I then wonder: how do you store that history?

There's an argument for this to be solved at the protocol level but I'd also like to explore how to solve this at the lexicon level too.

[snarfed]

Seconded that this is a very protocol-level, lexicon-independent use case. It was already in the protocol for a while, and functional, but got demoted so that they could do full deletes, and they haven't prioritized bringing it back. I definitely get the desire for having it sooner rather than later, and not waiting on them! But I'd encourage you all to think hard about how high priority it is for you, and whether you really want to try to bolt it on at the lexicon/app level, instead of maybe waiting a bit, nudging them more, and seeing where they're at.