Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PCAS (PEPFuture) message from PaDS #21

Open
nrshapiro opened this issue Jan 21, 2022 · 4 comments
Open

PCAS (PEPFuture) message from PaDS #21

nrshapiro opened this issue Jan 21, 2022 · 4 comments
Assignees

Comments

@nrshapiro
Copy link
Contributor

nrshapiro commented Jan 21, 2022

The PaDS portion of this message on Stage will look a bit odd to users (the part in parentheses, which comes from PaDS).

PCAS is the only journal that's in PEPFuture on Stage.

"""
This journal is in the process of being added to PEP-Web. This is content planned for the next release. It may be available on the publisher's website here. (Details of Item:PCAS can't be found on PaDS.)
"""

(A data update was recently run...it completed...not sure if it's a matter of PaDS in between updates or what.)

@jwoosnam
Copy link
Contributor

From what I understood, and I thought was happening previously, all journals should be on pads even if they are future journals. The journal PCAS is not on PaDS.
If I try https://stage-api.pep-web.org/v2/Metadata/Journals no PCAS is returned.

@nrshapiro
Copy link
Contributor Author

@jwoosnam

Yes, I was just thinking about that...yesterday, I made a change to the active journal flag so PEPFuture documents could be excluded from the statistics/journal count. There must be a view on Stage I need to update. Let me look into that.

@nrshapiro
Copy link
Contributor Author

nrshapiro commented Jan 22, 2022

@jwoosnam

Stage was updated last night, after fixing this issue (return of PCAS). I assume the reload of PaDS info was called automatically at the end of that (good test to see if that's true.) But FYI still getting the error this morning though.

image

@jwoosnam
Copy link
Contributor

jwoosnam commented Jan 24, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants