#mundaneum — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #mundaneum, aggregated by home.social.
-
@wallingf Advent of Computing podcast has two episodes on Otlet.
The first is https://adventofcomputing.libsyn.com/episode-107-the-mundaneum-part-i
-
Busy day for heritage fans!
Wikimedia Belgium is at the ODIS Meeting Day in Antwerp: chatting about databases, browsing archives, and getting lost in history. 📚
And tonight? Then it gets mysterious in Mons, where the Mundaneum opens its doors for La Nuit des Archives. 🌙🗃️
-
Busy day for heritage fans!
Wikimedia Belgium is at the ODIS Meeting Day in Antwerp: chatting about databases, browsing archives, and getting lost in history. 📚
And tonight? Then it gets mysterious in Mons, where the Mundaneum opens its doors for La Nuit des Archives. 🌙🗃️
-
Douche froide pour les centres d’#archives privées en #FWB (🇧🇪) : Il n’y aura pas, dans l’immédiat, de revalorisation budgétaire des centres d’archives privées (Archives et musée de la littérature, #Mundaneum, Archives d’architecture moderne, etc.) car le #budget nécessaire n’a pas été programmé par le gouvernement précédent... 🫣
https://www.lesoir.be/635427/article/2024-11-12/douche-froide-pour-les-centres-darchives-privees
-
Whitespace in filenames is a major category error IMO.
OTOH, filenames themselves (and filesystems as presently incarnated) are also grossly insufficient for many needs. It's interesting to note, for example, that on Android (and possibly iOS), databases (usually sqlite) have emerged as the de-facto default persistent data storage mechanism, even for content which would normally be held on a filesystem.
I've long been looking at questions such as what a document-oriented filesysem (#docFS) or the World Wide Web as fileystem accessible (#webFS) might look like.
For documents, I've generally arrived at a naming standard which uses underbars (_) to separate elements, hyphens (-) for standard whitespace, and double dashes (--) to indicate punctuated / multiple element (e.g., multiple authors, or a subtitle following a colon or dash). Permitted characters are otherwise 7-bit ASCII alphanumeric ([A-Za-z0-9], with dot as a file extension only, and possibly parentheses.
So:
Author-One--Author-Two_Title--Subtitle_YYYY.filetypeThat might have a publisher or journal title added (additional underbar-delimited element after the title(s). Additional contributors (e.g., editors, translator) might be mentioned. And it's possible some identifier (ISBN, OCLC, DOI, LoC call number) might be added, though those are supplemental.
The idea isn't to fully and completely or precisely represent all aspects of a document or work, but to usefully do so. So yes, that means that foreign charactersets aren't presented, that full author lists aren't included (for scientific paper these can number in the tens to hundreds), etc. But enough to find the work reasonably within a corpus through a directory listing.
Yeah, I'm familiar with Calibre, Zotero etc., and should really get more familiar with them. But they're clunky enough and not sufficiently universally available (e.g., on Android, where most of my documents live these days, via an e-book reader) that I'm not optimistic they're really a solution.
(Hoisted from a limited share.)
#DocumentManagement #Whitespace #OnTheNamingOfCats #OnTheNamingOfFiles #Whatever #SameThing #RockyHorror #MacavitysNotHere #Bombalurina #Effanineffable #OldPossum #TSEliot #DOS #PaulOtlet #Mundaneum
-
@Researchbuzz The proximity element is limited as I am, of course, on Altair IV, some 20 of your light years away.
That said, one of my obsessions (though not necessarily a major element of my Mastodon tooting) is information, knowledge, and document management.
The tags #kfc, #webfs, and #docfs will lead to a few of my information-management / search toots / threads.
And if you've got opinions, feelings, and/or deep intel on #PaulOtlet and his #Mundaneum I'm all ears.
