MathSciNet translator no longer working

aviness

As of June 19th, 2023, mathscinet has received a major design update. As a result, the Zotero connector does not choose the correct translator, even in legacy webpage.

I assume this is because:
- with the new design, the translator cannot read the metadata
- with the old design, the link to the page has changed, so the translator cannot be found.

------------------------------------

Debug log for the new design:
(3)(+0000334): Translators: Looking for translators for https://mathscinet.ams.org/mathscinet/article?mr=4399410

(4)(+0000015): Translate: Binding sandbox to https://mathscinet.ams.org/mathscinet/article?mr=4399410

(4)(+0000022): Translate: Parsing code for unAPI (e7e01cac-1e37-4da6-b078-a0e8343b0e98, 2019-06-10 23:11:21)

(4)(+0000010): Translate: Parsing code for COinS (05d07af9-105a-4572-99f6-a8e231c0daef, 2021-06-03 14:25:00)

(4)(+0000010): Translate: Parsing code for Embedded Metadata (951c027d-74ac-47d4-a107-9c3069ab7b48, 2023-04-25 01:30:00)

(3)(+0000003): Translate: Embedded Metadata: found 8 meta tags.

(4)(+0000026): Translate: Parsing code for DOI (c159dcfe-8a53-4301-a499-30f6549c340d, 2023-03-12 01:55:00)

(3)(+0000001): Translate: All translator detect calls and RPC calls complete:

(3)(+0000001): No suitable translators found

------------------------------------

Debug log for the legacy design:
(3)(+0000169): Translators: Looking for translators for https://mathscinet.ams.org/mathscinet/2006/mathscinet/search/publdoc.html?pg1=ISSI&s1=458117&sort=Paging&vfpref=html&r=3&mx-pid=4399410

(4)(+0000016): Translate: Binding sandbox to https://mathscinet.ams.org/mathscinet/2006/mathscinet/search/publdoc.html?pg1=ISSI&s1=458117&sort=Paging&vfpref=html&r=3&mx-pid=4399410

(4)(+0000018): Translate: Parsing code for HighWire 2.0 (8c1f42d5-02fa-437b-b2b2-73afc768eb07, 2022-06-14 16:40:00)

(4)(+0000008): Translate: Parsing code for unAPI (e7e01cac-1e37-4da6-b078-a0e8343b0e98, 2019-06-10 23:11:21)

(4)(+0000013): Translate: Parsing code for COinS (05d07af9-105a-4572-99f6-a8e231c0daef, 2021-06-03 14:25:00)

(4)(+0000011): Translate: Parsing code for Embedded Metadata (951c027d-74ac-47d4-a107-9c3069ab7b48, 2023-04-25 01:30:00)

(3)(+0000001): Translate: Embedded Metadata: found 3 meta tags.

(4)(+0000002): Translate: Parsing code for DOI (c159dcfe-8a53-4301-a499-30f6549c340d, 2023-03-12 01:55:00)

(3)(+0000003): Translate: All translator detect calls and RPC calls complete:

(3)(+0000000): No suitable translators found

adamsmith

Looking at this

adamsmith

@dstillman -- I have a working translator for the new site ready -- basically no overlap with the old site, which remains available in legacy under a new URL schema. Two options:
1) I kind of uncomfortably combine both translators into one (will make everything a bit more complicated because I need to constantly check on which version I am when running code)
2) a) I fix the target of the existing translator for the legacy site and add the new one as a new translator
b) I replace the existing translator with the new one, so that the main MathSciNet translator keeps the same ID, and move the old one with fixed target to a new ID.

I'd have a preference for 2a) or b) (and would probably do 2a), but wanted to check before spending time on going in any particular direction

dstillman

2a is good.

adamsmith

OK, the translator is now working for both the legacy site and the new one