Email or username:

Password:

Forgot your password?
ajft's posts Post Back to profile
Top-level
ajft

@samhainnight I have two middle names, once long ago a friend was working at the admin section of the uni I studied at, she found two files of my records, "Lastname, Firstname, middle1" and "Lastname, Firstname, middle2". One of these folders had one piece of paper, the other one had everything else. I believe she quietly merged the two and threw out one (allegedly, unofficially, etc)

23 October at 0:21 | Open on aus.social
2 comments
Moz

@ajft @samhainnight when I asked for my police records using FOI I eventually got three back because apparently the cops couldn't spell my last name. The first one I got back had it misspelled (but the record was me) so I asked again using common misspellings and got more matches :)

23 October at 1:03 | Open on fosstodon.org
jack is updating your database

@moz @ajft @samhainnight having worked in system administration in vaguely similar spaces it feels very bad to prematurely merge potential duplicate records because they usually cannot be gracefully unmerged if you've made a mistake

I've had fantasies of making a CRM where, instead of a person's record being this monolith and everyone/everything's updates being mixed in irretrievably, all the updates are marked with how the user identifies the subject:

"Joe Bloggs, owner of joebloggs@gmail.example"

"Joe Bloggs, subject of record ID 24601 in the old system"

"Joe Bloggs, resident at 22 West Wallaby Street"

"Joseph Bloggs, resident at 22 West Wallaby Street"

and if it transpires some of these identifiers are for the same person, you can link them and the users see a combined record with all the updates made against all the linked identifiers. but if it turns out you made a mistake you can unlink the identifiers and separate the Joseph Wallaby casenotes from the Joe Wallaby casenotes

@moz @ajft @samhainnight having worked in system administration in vaguely similar spaces it feels very bad to prematurely merge potential duplicate records because they usually cannot be gracefully unmerged if you've made a mistake

I've had fantasies of making a CRM where, instead of a person's record being this monolith and everyone/everything's updates being mixed in irretrievably, all the updates are marked with how the user identifies the subject:

23 October at 10:08 | Open on beige.party
Go Up