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
get_bnf_entry_from_isbn: add edition contributors #673
Conversation
@@ -6,7 +6,7 @@ import { forceArray } from '#lib/utils/base' | |||
import getInvEntityCanonicalUri from '../get_inv_entity_canonical_uri.js' | |||
import properties from '../properties/properties_values_constraints.js' | |||
|
|||
export default async (claims, resolveOnWikidata = true) => { | |||
export async function resolveExternalIds (claims, resolveOnWikidata = true) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah thx for that, much more greppable with named function
export async function setEditionContributors (edition, property, urls) { | ||
const uris = await resolveContributors(urls) | ||
if (uris.length > 0) { | ||
edition.claims[property] = uris |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a common pattern of seeds sometimes assigning translators as P50. But this will not conflict with the possibility of already having those authors in the P50 claim, right? aka BNF based entity creation is not based on the seed, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That should not conflict, as far as I can tell
wanted to rebase and merge, but tests need a functionnal BNF API which is not the case at the moment |
47bdd22
to
9b7a98e
Compare
9b7a98e
to
80cf9ae
Compare
Namely: translators, preface and postface authors