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

Validator should report invalid PIDs via structured logging #635

Open
matthew-morris-cessda opened this issue Feb 1, 2024 · 4 comments · Fixed by cessda/cessda.cmv.console#64

Comments

@matthew-morris-cessda
Copy link
Contributor

No description provided.

@matthew-morris-cessda
Copy link
Contributor Author

URNs should be treated as valid PIDs

@Joshocan
Copy link

Joshocan commented Mar 25, 2024

Validation records should have the following fields:

  • PID validity (Boolean type )
  • PID type ( handle, urn, doi, ark, etc)
  • PID agency ( Resolution agency)
  • PID reference (address)

@Joshocan
Copy link

We need to have separate fields for the elements in the pid_reports, i.e., pid_validity, pid_agency, pid_type, etc.

@Joshocan Joshocan reopened this Mar 25, 2024
@Joshocan
Copy link

List elements within valid_pid_report or invalid_pid_report fields appear as strings separated with commas in Elasticsearch.

@matthew-morris-cessda

As discussed, can you separate pid_type, pid_agency and pid_address from the valid_reports or invalid_reports objects

Screenshot 2024-03-26 at 14 57 51

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