#artbase — Public Fediverse posts

Since image management in Wikibase is so painful, pictures in #ArtBase will come from Immich instead: album names just start with the QID of the item they're associated with.

This week I presented to the Wikibase Stakeholder Group @wbstakeholders about the challenges of creating 5000+ lines of Shape Maps for RDF validation via rudof, and today the Query Shape Maps feature landed, with just documentation missing:

https://github.com/rudof-project/rudof/issues/387

Amazing work by José Emilio Labra and the WESO team!!

@thgie

#ArtBase

I was able to write Shape Expressions for most types of items in Rhizome's #ArtBase and validate them using rudof! https://rudof-project.github.io/

Boiling the ocean with RDF data validation
#ArtBase

Data in #ArtBase is quite incomplete. Displaying a minimum narration anyway is one of the challenges for the refresh.

This is a prototype of a timeline of an artwork that Rhizome doesn't even have a copy of. It was hosted on GeoCities (as per the URL the artist submitted). An events database is matching it with the date of GeoCities' closure. The Wayback Machine then finds a redirect to a new domain, but no other information about it, so it is drawn as "fading out" some time later.

Current state of the #ArtBase data model (at least the class hierarchy) can be viewed at https://tinyurl.com/2c7uofkr — sorry for link shortener, that's how the Wikibase query service works 😅

With the current #ArtBase setup I need to be proficient in Lua, PHP, Python, HTML, Docker, SPARQL, and bash. <https://digipres.club/@despens/105508279785415448>

For the setup I'm working on, I'll need proficiency in SPARQL, Gotemplates, HTML/JS/CSS, Python, Docker, and Bash. Scratching Lua and PHP seems like such a relief!

For piloting the site locally, I'm using Qlever, a new, amazingly fast SPARQL service <https://qlever.cs.uni-freiburg.de>. Just like Wikidata, Wikibase is using Blazegraph for SPARQL, but that's kind of abandonware and requires so much configuration. I hope to replace the public Blazegraph server with Qlever as well.

#ArtBase

So the renewed Artbase will be rendered by @abbe98's snowman <https://github.com/glaciers-in-archives/snowman>, a static site generator for SPARQL backends. As with most SSGs, the templating is super flexible (using gotemplates).

Which means the data model doesn't need to take into account the crutches required to read anything with Mediawiki's built-in Lua interpreter. Awesome!!

#ArtBase

Mediawiki is designed to help a staggering amount of users to not accidentally screw up the site, which means most HTML tags being filtered out, changing CSS take lots of effort etc.

According to a very small sample size, most Wikibases aren't open for editing by the general public <https://wbstakeholder.group/projects/data-stewardship-policies>.

Anyway, I wrote an absolute monstrosity of a templating system in Lua and patched Mediawiki to make it display at least some sort of layout, but that's not going to last.

#ArtBase

In general, the data model needs a bit of an overhaul. It is very much designed with the severly limited capabilities of Wikibase for data retrieval in mind. Wikibase itself cannot run SPARQL queries. There's an extension that can do it to some extent <https://professional.wiki/en/extension/sparql> but then I still have to deal with the super-basic presentation capabilities of Mediawiki.

#ArtBase

I'm currently working on revamping Rhizome's Artbase public collection/archive. It is running on Wikibase, we offer a SPARQL endpoint, etc. There are several issues to tackle and I'll post about them from time to time. #ArtBase

Where are my equine gents? My next base is a masculine anthro horse (or unicorn!) with a whole bunch of different options.

https://www.aubrietarose.art/shops/

#furryArt #base #artBase #adoptableBase #adoptable #lineart #lineArtBase #horse #horseFurry #anthroHorse #unicorn

Highlights from @despens's 'In Between Performance and Documentation' keynote yesterday:
"1. Everything is software.
2. Software preservation means providing continuous access to reproduced software performance." - these are the rules :)

From there we looked at singular object vs collection perspectives (loved the pyramid of dependencies graphic ⚠️) as well as modes of preservation that deal with: a) actively developing software to keep it running; b) maintaining environments to run specific software that is itself no longer developed; c) packaging together software and environments and managing only how those package interface with external components (aka emulation-as-a-service). The last mode is most efficient from collection perspective & was beautifully demoed with works by Auriea Harvey (aka Entropy8), and thanks to the encapsulated environment approach, other web resources from the open web archives contemporaneous to the work (e.g. the amazon of the mid 90s) could be called up during the demo session.

Next things on the wishlist... get EaaS data as LOD✨ & sync up with the rest of the #ArtBase archive data 😅

Looking forward to seeing the exhibition 'Docu & Demo: Archiving Programmed Media Art' at Collegium Helveticum and hearing @despens's keynote later today. 💻

Tomorrow I'll be talking more on the roles of #Wikibase and LOD✨ as media preservation tools in the case of Rhizome's #Artbase in particular, as well as in broader context's such as some of the use-cases examined with @nfdi4culture.

The workshop tomorrow will be hybrid, link to join is accessible on the event page 🔗 https://collegium.ethz.ch/veranstaltungen/?event=14058&cat=upcoming

Vanavond de eerste vergadering van #RaadEde na het zomerreces. Vanaf 15:00 uur staan diverse belangrijke onderwerpen op de agenda, waaronder de stand van zaken rond #ArtBase, uitbreiding bedrijventerrein De #Stroet in #Lunteren en gebiedsontwikkeling De #Ginkel.
https://ede.raadsinformatie.nl/bijeenkomst/1062255/Politieke%20Dag%20Ede%2007-09-2023
Over de uitbreiding van De Stroet schreef ik een opiniestuk voor de #EdeseVos: https://edesevos.nl/uitbreiding-lunters-bedrijventerrein-ten-koste-van-groen-voedsellandschap/

#GemeenteEde #Ede

In the chapter, I talk about the #ArtBase redesign started with
@Rhizome and @despens back in 2016, and what could be next steps for software archives when screenshots are read as data sources (and not just static captures of what happens on a screen). Message if interested in proof PDF.