could you be a bit more specific? are you asking about backup best practices, or designing a project so that the data is future proof and accessible?
I know some things about the latter, but most of what I've learned I've picked up from people in the field.
if what you're asking about is the way to take a set of historical records, edit them, and publish them in a robust and futureproof digital format, I think most people would agree that TEI-XML is the currently the standard for scholarly textual markup, which can then be served to users in a variety of ways
detailed examples here:
XML presupposes you're OK with data in a hierarchical data model. if you're working with literary texts this can be problematic
Scholar Social is meant for: researchers, grad students, librarians, archivists, undergrads, academically inclined high schoolers, educators of all levels, journal editors, research assistants, professors, administrators—anyone involved in academia who is willing to engage with others respectfully.
We strive to be a safe space for queer people and other minorities, recognizing that there can only be academic freedom where the existence and validity of interlocutors' identities is taken as axiomatic.
"A Mastodon profile you can be proud to put on the last slide of a presentation at a conference"
(Participation is, of course, optional)
Scholar Social features a monthly "official" journal club, in which we try to read and comment on a paper of interest.
Any user of Scholar Social can suggest an article by sending the DOI by direct message to @email@example.com and one will be chosen by random lottery on the last day of the month. We ask that you only submit articles that are from *outside* your own field of study to try to ensure that the papers we read are accessible and interesting to non-experts.