Hi @joostholslag and sorry the mailarchive is not findable any more. I will look into where there could be a backup and see if it can be restored. It was running on the Sava ‘God’ server, which was doing a lot of things including the mailarchive. I will see what we have backups of and whether a restore can be done. I take full responsibility for this failure if the mailarchive can’t be restored. Apologies.
The mailarchive was something that was already deprecated before I started working for openEHR and I’ve never been involved with its running. In general such mailing lists can be imported into Discourse, but I don’t think this was ever done.
I’m very happy to work on an archiving strategy. My view would be to keep everything always, as long as it is still in a usable form, for example mailing lists, Slack and other similar messaging/forum/discussion archives should be kept running or imported into something that is still running eg. Discourse.
There’s a python Slack dump that thingy that is handy to archive Slack messages behond the free Slack limits. If anyone is interested, I can share details.
Thanks @Olly_Cogan - I think in the end, the owners of the openEHR Clinical Slack decided to completely deprecate it instead. I don’t think we extracted any content.
No problem, we moved away from Slack. The paid version was an additional overhead we coudl do without. I gambled that Google Chat would receive more iterative development (as was very basic at the time) and thankfully it has, is now very decent.
So we have everything covered under our Google Workspace licensing, helped to avoid multiple SaaS lock-ins!
As much of an appreciator I was of Slack in terms of UX, Google Chat is now quite adequate with added advantage that puts everything in one place for us, less admin, and everything just flows / plugs together across Google Workspace apps.
Besides, Slack lost all its appeal for me when Salesforce bought it!
Tom I and migrated the whole mail archive (I think almost all the way from early 2000s) to a pretty good mail service at some point after 2010s Then we took a backup of it before migration to discourse. I’ll check if I have any emails with attachments etc. There is some great discussions in that archive. It would be good to make it available if we can.
@thomas.beale you sent an email with the subject “[openEHR SEC] THIS LIST CLOSING SOON - MOVING TO DISCOURSE” to sec@lists.openehr.org on 13/03/2020 16:18 from your arssemantica account.
You said in that email: “I will obtain the complete archives of the SEC mailing list before it closes.” I think you ran the communications with Brian Carpenter from emwd.(c)om at the time of migration.
Just in case it help track down the archive files.
I’ll have to check on another computer where those files are, but I did get them. We previously had everything from the original lists (that ran at UCL) on a web archive site.
We did talk about it with Marcus when we first went to Discourse, but decided it was not worth it, in the sense that it wouldn’t add much to the capability of mail-archive.com. What might make sense is that for interesting discussions / posts that are visible in those archives, interested parties might manually transfer the useful parts to this platform - perhaps in a special sub-category under the main categories we have.
If there is appetite for importing the old posts I could revisit the idea. Importing .mbox files of archived mail content is fairly robust now in Discourse, 10+ years into the project. It would be nice to have everything in one place.
Hi Thomas. There’s a blog post here linked from the home page which covers the basics, without going into the technical aspects of the standard.
Search bar - yep, it’s on the list. P
Hi @Pete_Bouvier I recall previous comments about rather large random people’s faces on the home page. I personally like the use of text and visuals on web pages (and probably any other print or digital material) but I’d prefer not to have random real smiling faces highlighting full snow white dentures! Maybe gender/race etc. neutral avatars or other non-person visuals relevant to the topic (e.g. developers may have some form of technical imagery and clinicians - well something clinical…and images with much less kilobytes. All the rest looks awesome and thanks for all the hard work that went into putting a fresh and modern look
FIXED: These links have been fixed by setting up static files served at exactly the URL the Specifications page is expecting. We can use this pattern to fix any missing assets of any kind. It is sadly a bit of a manual process, but after this point they will just work. All these little exceptions or static files are being version controlled in the website config GitHub repo, which means any future move of website will bring them with us automatically.
