Entity pages for PERS1 and PROS1 bios

[martindholmes]

Create MoEML-style contributor pages for LEMDO (like mapoflondon.uvic.ca/ELHA1.htm). Currently we can access a pers id on the site as we would any id within another page (PERS1.html#ID), which takes you to the person within PERS1. We want standalone pages that actually represent the credits and responsibilties that we have been discussing.

We'll need to pull these into anthology builds where they are directly linked, but then preprocess them to remove any ongoing links to other bios which aren't part of the anthology.

[JanelleJenstad]

QME is now at the point of needing more than a soft release. Their old site isn't working well at all, so we'll want to replace it with the new static site when we do a release.

[martindholmes]

QME beta release has no date attached to it, and we don't have a detailed plan for the lead-up to it. Can we start putting that together?

Has something changed about how the old site is working?

[martindholmes]

Also, while we're looking at this ticket:

We know we need to build individual pages for each of the entities, but it's not clear what will link to them. In MoEML we have a set up where a popup has a title which constitutes a link to the static page for the entity. Should we do the same thing in LEMDO? Will there be any other ways of accessing the individual entity pages? Should they be indexed in the search?

[martindholmes]

@JanelleJenstad Any response to the question above yet?

[JanelleJenstad]

QME Release Date Let's set the QME Release milestone for August 31 (two months after they are supposed to get their peer review report for Selimus back).

The old staticized sites The annotations on the old ISE, DRE, and QME sites are popping up on the top left of the page and users have to scroll up to the very beginning of the page to read them. I got a few bug reports from people trying to use the sites to teach this term. I suspect it's something to do with the one of the external JS libraries having changed.

[JanelleJenstad]

Individual pages for entities

We know we need to build individual pages for each of the entities, but it's not clear what will link to them. In MoEML we have a set up where a popup has a title which constitutes a link to the static page for the entity. Should we do the same thing in LEMDO? YES

Will there be any other ways of accessing the individual entity pages? YES. If people know the URL, they should be able to go directly to a page with URL lemdo.uvic.ca/HOLM1.htm (to see your bio, for example).

Should they be indexed in the search? Yes please.

[martindholmes]

Good to have a date for the release. I'll be on vacation for the first part of August, but there should be time. Re the old sites: do we need to do anything about that, or is this part of natural degradation? If we have to fix it, is it ahead of fixing the PDFs in the priority list? And re this particular ticket: are the entity pages ahead of the PDF fix, or after it?

[JanelleJenstad]

I’d put it in the category of natural degradation and not do anything about it.

Janelle Jenstad, Associate Professor, Department of English, University of Victoriahttps://journals.uvic.ca/index.php/scene/ Director, Map of Early Modern Londonhttps://mapoflondon.uvic.ca/; Director, Linked Early Modern Drama Onlinehttps://lemdo.uvic.ca/ Co-Coordinating Editor, Digital Renaissance Editionshttps://digitalrenaissance.uvic.ca/ and the new Internet Shakespeare Editions Co-Applicant, The Endings Projecthttps://endings.uvic.ca/index.html Email: @.**@.>, @.**@.>, or @.**@.>

From: Martin Holmes @.> Sent: April 15, 2022 10:49 AM To: projectLEMDO/lemdoIssues @.> Cc: Janelle Jenstad @.>; Mention @.> Subject: Re: [projectLEMDO/lemdoIssues] Entity pages for PERS1 and PROS1 bios (Issue #5)

Notice: This message was sent from outside the University of Victoria email system. Please be cautious with links and sensitive information.

Good to have a date for the release. I'll be on vacation for the first part of August, but there should be time. Re the old sites: do we need to do anything about that, or is this part of natural degradation? If we have to fix it, is it ahead of fixing the PDFs in the priority list?

— Reply to this email directly, view it on GitHubhttps://github.com/projectLEMDO/lemdoIssues/issues/5#issuecomment-1100259573, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABNLCOHOEAYJZ63UA6M4DWTVFGTYJANCNFSM5PY33UWQ. You are receiving this because you were mentioned.Message ID: @.**@.>>

[martindholmes]

Coming back to this to devise a strategy, which I presume should be:

1. Generate the entity pages at build time. Work with @pszpak to make them look good before any links to them are created.
2. Make sure any referenced people's pages are copied into anthology output, and any links inside them to other entity pages which are not directly reference get unlinked.
3. Alter the processing of in-page person elements so that the heading of the popup is a link to the person page.
4. In a full build of lemdo-dev and another anthology, check that all links resolve.

[martindholmes]

This is currently blueSky because of the time it would add to the already very long build process.

[martindholmes]

@JanelleJenstad I believe this is now basically impractical because of the huge expansion of LEMDO beyond the original plan, and the consequent scale on which entity pages would be built, along with the load it would add to the build time. If we have our own LEMDO build server and we can rewrite the build process to build specific anthologies without the main build process, it might become practical again.

[martindholmes]

Coming back to think again about this: everyone does get a unique URL based on the PERS1 or PROS1 page:

PERS1.html#HOLM1

PROS1.html#MARL16

The only thing missing from there would be a list of links to all mentions of the person, but that isn't practical anyway because in any specific anthology a different set of pages will be available. But what we could do instead is provide a search-page name search field, which would enable anyone to find all the documents in the anthology relating to a specific person; and since searches are bookmarkable, we could perhaps add a link to that specific search into the person record. That would solve the problem for individual anthologies without adding a massive burden to the build process. @JanelleJenstad @LEMDO-PM what do you think?