Prosopo<re>Cogito

[Gabriel Bodard]

Dear all,

A quick survey (co-signed by the chairs of the LOD People activity):

Context: A few years ago we held a short hackathon over a couple of days, to implement person-data search in a fork of Recogito 2 (rather clunkily dubbed Prosopocogito). Rainer and Gethin and others tweaked the code, and a few of us created some sample data in a SNAP-inspired JSON format. The code hasn't been updated since about 2017 (and is obviously redundant given the development of New Recogito), but it was a useful exercise and thought experiment.

Question: In the opinion of Pelagians who know the New Recogito code base, how essential would the input of the original developers be in doing a similar experiment with person encoding, search and annotation in the new code?

More broadly, who would be interested in contributing to such a fork some time? Would anyone who is familiar with the new code be willing to give an introduction/orientation to a hackathon team? What might your desiderata for such an activity include?

Please feel free to respond offlist (or join the LOD people group) if we don't want to clutter the whole PN group's inboxes with this…

Best,

Gabby and Jun

-- 

Dr Gabriel BODARD (he/him)
Reader in Digital Classics

Director of Studies (research): Digital Humanities Research Hub

Director of Studies (research): Institute of Classical Studies

Mailing address:

  Institute of Classical Studies

  University of London

  Senate House

  Malet Street

  London WC1E 7HU

 
Due to new IT security rules, I am currently not able to read or reply to email outside of office hours, or while travelling or working from home. This may result in slower replies than usual.

[Rainer Simon]

Dear all,

<Would anyone who is familiar with the new code be willing to give an introduction/orientation to a hackathon team?>

As one of the core devs, I'm definitely happy to do that! However, in order for it to be useful, it will be essential for interested developers to first take a look at the code themselves, and find out if it's something they feel familiar enough with, in terms of the level complexity & tech stack. 

https://github.com/recogito/recogito-client

https://github.com/recogito/recogito-server

https://github.com/recogito/recogito-studio

To manage expectations: Recogito is neither a small codebase, nor your usual "database with a bit of HTML" type thing. The new tech stack is arguably way more standard than that of the old Recogito. (JavaScript ecosystem vs. an odd combination of a Scala backend, custom auth system, and a mess of legacy JavaScript.) But it's still a big application with many moving parts. You will need advanced web development expertise, and solid experience with TypeScript, React and various NodeJS/JavaScript technologies that surround it. (In other words: don't expect to be able to add a new feature by tweaking a few lines of code.)

There are also the beginnings of a "plugin framework" that we created, which is supposed to facilitate future extensions to Recogito Studio more easily. But it's early days for this. There's no proper documentation yet, nor an actual SDK or plugin development toolkit. But (within certain limits) the UI of the Recogito Studio annotation view can be extended with additional UI components, through a mechanism based on the React Supsense and lazy API. (Which means it's an advantage if you've already heard of it ;-) 

If anyone wants to pick this up - do feel free to get in touch with me (also off-list if you prefer), and we can talk a bit more about the details.

Best,

Rainer

--
You received this message because you are subscribed to the Google Groups "Pelagios Network Members" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pelagios-netwo...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/pelagios-network/LO0P123MB4140F0ED7297444EC231B698C16F2%40LO0P123MB4140.GBRP123.PROD.OUTLOOK.COM.

--

---

Sent from my Fairphone