{"action":"created","issue":{"url":"https://api.github.com/repos/zme1/toscana/issues/36","repository_url":"https://api.github.com/repos/zme1/toscana","labels_url":"https://api.github.com/repos/zme1/toscana/issues/36/labels{/name}","comments_url":"https://api.github.com/repos/zme1/toscana/issues/36/comments","events_url":"https://api.github.com/repos/zme1/toscana/issues/36/events","html_url":"https://github.com/zme1/toscana/issues/36","id":316915353,"number":36,"title":"Re-Tooling Code for Page-Aligned Reading Views","user":{"login":"ebeshero","id":4014518,"avatar_url":"https://avatars3.githubusercontent.com/u/4014518?v=4","gravatar_id":"","url":"https://api.github.com/users/ebeshero","html_url":"https://github.com/ebeshero","followers_url":"https://api.github.com/users/ebeshero/followers","following_url":"https://api.github.com/users/ebeshero/following{/other_user}","gists_url":"https://api.github.com/users/ebeshero/gists{/gist_id}","starred_url":"https://api.github.com/users/ebeshero/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ebeshero/subscriptions","organizations_url":"https://api.github.com/users/ebeshero/orgs","repos_url":"https://api.github.com/users/ebeshero/repos","events_url":"https://api.github.com/users/ebeshero/events{/privacy}","received_events_url":"https://api.github.com/users/ebeshero/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":14,"created_at":"2018-04-23T17:48:48Z","updated_at":"2018-04-26T02:07:02Z","closed_at":null,"author_association":"COLLABORATOR","body":"@zme1 Here's a quick summary of the high points of our meeting today:\r\n\r\n- [ ] You want to optimize the way your pages are aligning with your transcriptions and translations. For this we discussed:\r\n* Setting an `@facs` on your `<pb/>` elements so that you can point to the image URL for a page in your TEI. \r\n* Removing or dealing with the issue of multiple `<pb/>` elements for a single page when that page ends one set of minutes and begins a new one. \r\n* Dealing with the overlapping hierarchy issue of pages vs. minutes. For this, we discussed \"pipelining\" your transformation to make the reading view. Let's try writing an XSLT Identity Transformation that flattens the XML hierarchy so that `<p>` and the like are the largest containers, and changes in minutes **as well as** changes in pages are signalled with milestone-style empty elements. This makes it easier to output a precisely page-aligned reading view, while still signalling in the HTML a shift in minutes: You'll be able to set internal links (or navigation links) to move page-by-page OR minute-by-minute. \r\n\r\n- [ ] Personography and Family list: Pull the information on families involved in the Lega into your personography file, by preparing a `<listOrg>` as a preceding or following sibling of your `<listPerson>`. Once you've prepared the basic listOrg, let's try writing an XSLT Identity transformation to add pointers to the persons in your listPerson who are associated with each family. Here are [the TEI specs for `<listOrg>`](http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-listOrg.html).\r\n* I'd just start by creating a simple `<listOrg>` with `<org>` entries and assign each an `@xml:id` like you did with the `<person>` members of `<listPerson>`. Use the `<desc>` element (as you see in the TEI example) to hold the descriptions provided by your teammates from the Google Doc. \r\n* Then, when you're ready, let's work out an XSLT Identity Transformation that reaches around and associates all the people connected to a family. For this we'll want to work with [the TEI element `<listRelation>`](http://www.tei-c.org/release/doc/tei-p5-doc/en/html/examples-listRelation.html), which can sit at the end of either the `<listPerson>` or the `<listOrg>`, and exists specifically to say people are identified with a family--For the encoding these are all either \"passive\" or \"mutual\" relationships b/c, well, people didn't ask to be born to X family. ;-) \r\n\r\n- [ ] You want to produce a network graph of the committees, with committees as edges and people as nodes. "},"comment":{"url":"https://api.github.com/repos/zme1/toscana/issues/comments/384489692","html_url":"https://github.com/zme1/toscana/issues/36#issuecomment-384489692","issue_url":"https://api.github.com/repos/zme1/toscana/issues/36","id":384489692,"user":{"login":"ebeshero","id":4014518,"avatar_url":"https://avatars3.githubusercontent.com/u/4014518?v=4","gravatar_id":"","url":"https://api.github.com/users/ebeshero","html_url":"https://github.com/ebeshero","followers_url":"https://api.github.com/users/ebeshero/followers","following_url":"https://api.github.com/users/ebeshero/following{/other_user}","gists_url":"https://api.github.com/users/ebeshero/gists{/gist_id}","starred_url":"https://api.github.com/users/ebeshero/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ebeshero/subscriptions","organizations_url":"https://api.github.com/users/ebeshero/orgs","repos_url":"https://api.github.com/users/ebeshero/repos","events_url":"https://api.github.com/users/ebeshero/events{/privacy}","received_events_url":"https://api.github.com/users/ebeshero/received_events","type":"User","site_admin":false},"created_at":"2018-04-26T02:07:02Z","updated_at":"2018-04-26T02:07:02Z","author_association":"COLLABORATOR","body":"@zme1 Sounds like you've got this figured out in your own way--and you know your data. What I see here is XML, so I take it this is a preliminary to constructing a new reading view for the web--and as long as you've got a system mapped out that makes sense to you and tightens up the pagination (so you're not duplicating it unnecessarily) that sounds consistent with what we discussed. "}}
{"actor":{"display_login":"ebeshero"}}