Publications appearing in DOI Verification bucket but not in All Publications bucket

[anaelizabethenriquez]

There are currently two publications appearing in the DOI Verification bucket for which the file is listed as "Not Found":

• X-Shooting ULLYSES: Massive stars at low metallicity: IV. Spectral analysis methods and exemplary results for O stars
• X-Shooting ULLYSES: Massive stars at low metallicity III. Terminal wind speeds of ULLYSES massive stars

Each publication has an Activity Insight OA file record associated with it, but when I try to download the actual files, I can't.

Another odd thing is that neither of these publications shows up in the All Workflow Publications bucket.

[anaelizabethenriquez]

@ajkiessl This is the ticket I was trying to think of at stand-up.

[ajkiessl]

@anaelizabethenriquez Here are my findings:

1.) The DOIs we receive from external sources (these have Pure and Activity Insight imports) are found in Unpaywall. However, the title stored in Unpaywall is just "X-Shooting ULLYSES: Massive stars at low metallicity" for both of these. This does not match with what we have in RMD, so the DOI verification fails.

2.) Since we do have DOIs (albeit not verified), we receive the open access statuses from Unpaywall. The open access status for both of these is "hybrid". We generally filter these out of the AI OA Workflow, but we do not filter them out of the DOI verification check table. This may have been because we want to confirm we are getting the right info from Unpaywall first. This is mentioned here: #797 (comment)

3.) Also, since the open access status is "hybrid" for these, the AI OA File records are filtered out of our process for downloading the actual file from Activity Insight. So, you cannot download and view the file.

4.) Again, since the open access status for these is "hybrid", they are filtered out of the "All Workflow Publications" bucket.

[anaelizabethenriquez]

Thank you very much. This all makes sense, and it's very helpful to have it documented here. I think you can close this issue in whatever appropriate way since this is not a bug.