search

Psychoanalytic-Electronic-Publishing / PEP-Web-User-Interface

Single Page App Graphical User Interface for PEP-Web
1 stars 0 forks source link

PD- PD_32_6 (2022) Large number of headers missing - client issue? #745

Open SophieMBennett opened 1 year ago

SophieMBennett commented 1 year ago

Psychoanalytic Dialogues

https://stage.pep-web.org/browse/PD/volumes/32 https://www.tandfonline.com/toc/hpsd20/32/6?nav=tocList

PD 32-6_1 PD 32-6_2 PD 32-6a PD 32-6b PD 32-6c

nrshapiro commented 1 year ago

@SophieMBennett @jordanallen-dev @ocappello

The missing section header, at least above PD.032.0278A, is not a data problem.

This is due to a small workaround for the repeating section header issue I did some months ago since we weren't getting anything done by Gavant in the client. Unfortunately, the workaround doesn't work when an issue has more than one "duplicate" heading, like Article. That's not something I expected.

Now that we have Client development back in play, I'm going to remove it from the server, and let the client deal with the repeats, since the pages are sequential when building a TOC. That also means that we can allow the section headers to show in the article at the top right (as they do in print, at least) as well. A better solution.

I've seen repeating section names in some issues anyway, so it would be good to have Jordan look at getting it fixed once and for all in the client.

After the server stops removing section headers it thinks are repeats (e.g., for the issue), at least you'll know when Aptara hasn't keyed one.

I'm going to assign this to Jordan. Note that the server needs to be updated online before this can be fixed, and I'm not quite ready to post a new version since I'm working on the reference linking and I have table changes that could break things!

nrshapiro commented 1 year ago

@SophieMBennett @davidtuckett @ocappello @jordanallen-dev @nadinelevinson

This is fixed in our system to the extent that articles are now correctly placed in the category, as long as the newsecnm info is correctly coded.

However, note that the client resorts the article and organizes the sections "by section". This is not the order Taylor and Francis uses, and perhaps not the best order to provide the contiguity of "article - discussion - response". That could be revisited, but the logic of reorganizing would be a bit complex since the client would have to consider the semantics of the section name, and then sort by page number.

The T&F section naming is also a bit awkard because there are so many section headings.

To my mind, the best way to so this is to introduce section levels.

Article is a section level. Discussion is a subsection and could also include response, or it could be a subsection label as well, though I don't think it's necessary. (T&F may in fact be doing this since ARTICLE is all upper case, and Discussion and reply are mixed case), and seem to be "grouped" by shading.)