Open cessda-bitbucket-importer opened 2 years ago
Original comment by John Shepherdson (GitHub: john-shepherdson).
What about the case where an endpoint has multiple sets, one per publisher?
Original comment by John Shepherdson (GitHub: john-shepherdson).
Not enough time and not enough utility to include in v3.0.0
Original comment by John Shepherdson (GitHub: john-shepherdson).
Moved to v3.2.0 release, after discussion with Service Owner on 15/09/2022
Original comment by Matthew Morris (GitHub: matthew-morris-cessda).
Just to be clear, this is for the seach filter? The display of the publisher on the detail page was resolved in #430.
Original comment by John Shepherdson (GitHub: john-shepherdson).
For the filter, but we first need to check the Publisher values being supplied by e.g. Progedo as they should correspond to values in https://vocabularies.cessda.eu/vocabulary/CdcPublisherNames?lang=en. If not, we need to consult MDO before implementing this.
Original comment by Matthew Morris (GitHub: matthew-morris-cessda).
ProgedoSciencesPo supplies:
Original comment by John Shepherdson (GitHub: john-shepherdson).
None of which match the current CV
ProgedoCDSP PROGEDO: Center for Socio-Political Data (CDSP)
ProgedoCNRS PROGEDO: CNRS
Progedo PROGEDOFrance
So no action. We need to take advice.
Original report on BitBucket by John Shepherdson (GitHub: john-shepherdson).
Because of the historical variability of the values used in the Publisher field (/codeBook/stdyDscr/citation/distStmt/distrbtr for DDI 2.5), all records from a given endpoint are attributed to the same Publisher via a simple mapping.
Recent activity by some SPs (Progedo, for one) has resulted in multiple (clean) publisher values appearing in records from the same endpoint. In such cases, we should have the option to use the provided values, rather than the default ones.