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

GoldStandard table should qualify the source system associated with the accepted or rejected object #337

Open
paulalbert1 opened this issue May 3, 2019 · 0 comments

Comments

@paulalbert1
Copy link
Contributor

paulalbert1 commented May 3, 2019

The GoldStandard table is overly PubMed-centric. As we prepare to track from feedback from N other source systems (Scopus, WorldCat, etc.), our syntax shouldn't presume that every record is from PubMed.

Top level nodes

I suggest we change the data model for top level nodes from:

{
  "auditLog": [
    ],
  "knownpmids": [
    ],
  "rejectedpmids": [
  ],
  "uid": "jobuck"
}

to:

{
  "auditLog": [
    ],
  "PubMed": [
      "accepted": [
       ],
      "rejected": [
       ],
  "Scopus": [
      "accepted": [
       ],
      "rejected": [
       ],
  "uid": "jobuck"
}

There's probably no need to create Scopus or any other source system until we get feedback from this user.

Audit log

Here, I suggest we go from:

  "auditLog": [
    {
      "action": "ACCEPTED",
      "dateTime": "2019-04-26T16:07:57.179Z",
      "pmids": [
        10869379
      ],
      "uid": "jobuck",
      "userVerbose": "Jochen null Buck "
    },

to:

  "auditLog": [
    {
      "action": "ACCEPTED",
      "dateTime": "2019-04-26T16:07:57.179Z",
      "objectId": [
        10869379
      ],
      "source": "PubMed",
      "uid": "jobuck",
      "userVerbose": "Jochen null Buck "
    },
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

1 participant