ajaxmulticommentary / ajmc-elixir Goto Github PK
View Code? Open in Web Editor NEWHome Page: https://ajmc.unil.ch
License: GNU General Public License v3.0
Home Page: https://ajmc.unil.ch
License: GNU General Public License v3.0
To be then shared with Luca and Mahmoud.
URL template: https://ajmc.unil.ch/tei/{commentary_id}.xml
Find a better default zoom level (a bit more zoomed out than it is now).
This is related to the OSD IIIF viewer.
With data ingestion step.
e.g., in the page http://0.0.0.0:4000/bibliography/DeRomilly1976
https://wikidata.org/Q118976611
should rather be https://wikidata.org/wiki/Q118976611
In order for this to happen, it's necessary to ingest all available lemmata annotations into the canonical JSONs. So, all other commentaries (but Jebb) will need to be re-canonified so that these annotations will be picked up by the backend API and finally be displayed in the application. On the inception-side of things, all available annotations were exported to XMI (see this commit https://github.com/AjaxMultiCommentary/lemma-linkage-corpus/commit/4e949614345443d397c3df6386cc095da214219f).
We need to define API endpoints for browsing and searching lemmas for commentaries.
We can start with Jebb, as the data are mostly ready to go.
/commentaries
API endpoint/commentaries/:commentary_urn
API endpoint/commentaries/:commentary_urn/comments
API endpoint/commentaries/:commentary_urn/lemmas
API endpoint/commentaries/:commentary_urn/comments?search=my%20query
?)@pletcher Just an idea, let's discuss
As a user, it'd be useful to know (at a glance), at all times, how many glosses are available for the text section in focus and how many am I currently viewing (e.g., as a result of filtering).
Possible template: Currently displaying X glosses from X commentaries for this section (lines x-y). In total, there are Y glosses (of which Z are lemma-less).
Once #20 is fixed, quite a bit of space will be freed up in the top horizontal part (i.e. above the horizontal grey lines)., so this could be easily added.
JSON data for the synopsis is here.
Behaviour: the entire text will be loaded, but when clicking on a synopsis section the reading focus (= text window in focus) will ‘jump to’ the desired section.
steps to reproduce:
Some thoughts:
Needs further discussion:
As a user I'd like to:
Features: OCR + image display
This can perhaps be offloaded to existing tools, e.g. TEI Publisher
For debugging of data it would be super useful. It could be hidden behind a small button or something. For a given glossa, I'd like to know what is the corresponding page image number.
Even better: make the page number a link to the IIIF page image for a quick check (I know there is the OSD viewer, but it makes the page number transparent, which is instead useful for debugging)
Just happened to notice that Campbell's commentary (cu31924087948174
) does not show up in the interface. However, it's listed in https://github.com/AjaxMultiCommentary/ajmc-multicommentary/blob/main/priv/commentaries.toml
(to be sketched out)
About
should be added (with localised versions)NB: the Meta-Commentary menu item will be a placeholder for functionalities to come in next releases
As a user, I'd like to have direct links to individual commentary lemmata. This requirement could be satisfied if we had a CTS URN for each lemma, and to have the reading environment respond when it gets a reference like that in the URL.
TODO: sketch out what the desired behaviour will be
some design changes to the filter (as discussed yesterday):
PS: can we have in brackets, beside the commentator's name, the total number of glosses existing for the text section in focus?
This refers to the content of the html > head > title
element in the various pages. It's a small detail, but it becomes "visible" whenever pages get bookmarked.
For links to the ajmc platform that point to a specific glossa, I guess the title could/should reflect the target glossa, but we can leave this, in case, for the minimal comp. version.
Bibliography will be one item in the main menu.
In this basic version, I'd like to have displayed bibliographic metadata for the commentaries in our corpus, which should be fetched from this Zotero library. Short labels in the multi-comm. reading environment (e.g. Finglass 2011) should link back to the corresponding record in this section.
The easiest, I guess, is to hide those details behind a button. But I let you decide how to implement this.
There is a dependency with this ingestion pipeline issue: AjaxMultiCommentary/ajmc-pipeline#16
It'd be great to be able to edit some pages via Markdown. For now this applies to the to-come About page but there may be more use cases in the near future.
As an example, Stanford’s glossa to lines 160-1, is rendered as if it was referring to lines 1-160. It seems to be happening also for other glosses.
Add some info buttons to provide the users quick explanations of how key interface components work.
Info buttons for:
Explanations attached to info-buttons should be localised
Not sure what would be the best to place this new button. Perhaps in the middle column, on top of the critical text?
At all times, the user should be able to ‘switch on/off’ glosses from a given commentary, filtering of glosses based on comm.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.