@e_stanf One last quote, but it's my fave, on a review of two early music recognition dissertations: "a machine that ‘reads’ multiple parallel staffs bearing ... printed music in at least one ‘fount’ and size [is] no further than another couple of MIT dissertations away." (Kassler 1972)
@EthanWatrall There's also the Mapping Manuscript Migrations project, which looked at MSS provenance information across three DBs: https://t.co/2emhpgT8mp
@EthanWatrall The Schoenberg Database at UPenn is a provenance database of MSS provenance: https://t.co/dbW42w3nWo
The Bodleian has some TEI provenance information in its Medieval MSS, e.g., https://t.co/1phs6oeyuv
Hello everyone! This is the Twitter account of the Music Encoding Conference 2021, which will be held in Alicante from the coming 19th of July to the 22nd. We will use this account to keep you posted on the news of the event and all related stuff. Looking forward to meet you all!
@azaroth42 When I log in I seem to get a bunch of controls, one of which is “add statement” in the vocabulary section. I can also edit existing statements.
@e_stanf For DB2, building our own solution wasn’t the first option. It was only after looking at the available alternatives, and the available skills on our team, that we made the call to go another way. We both know projects who made a diff call and I still think ours was the right one.
@e_stanf Does it use Blacklight/Samvera? —> Yes —> Build sth different.
Choosing a pre-built tool isn‘t the solution to obsolescence, since for any moderately complex org the effort remove and add the things that don’t work for you ~= the effort to build something from scratch.