[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Reply to: [list | sender only]
Expanding category key for publ_author.name
- Subject: Expanding category key for publ_author.name
- From: James Hester <jamesrhester@xxxxxxxxx>
- Date: Fri, 28 Jun 2019 14:37:42 +1000
- DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;h=mime-version:reply-to:from:date:message-id:subject:to;bh=clFw5Iuw9IOiOLV8n/4fBDuFaKwcQw67T+bTlqbgx4A=;b=h0zAh9Lu41CjWVXbvHv0ViId/VKKkJOm4eURcLj8P9kd85YL6teVRqT3WLvLu5oHMjqJ1lfHYQj9hhB+/87CwutU9yeieYlFcHmnuFbLrPPeMyAbphydXDvLNLWbeY+ByZkhh0mE6/5DPgtf1eVHbPHQm4UWP+H4G6vtL1PEZXGKtbXQgS6LkYYvK24jeSOpdu+BUiyKUFKsRQMyFIKklJ8CYoCuww9bfDO7OgPHSmb1nUlwyzmsYuxo9dtnT9lVzK3Jq6N2vlBG/RCe5ruP7yBsRe8DcCKLKtuv6z9BKu9a7augvY0p0NDihR0iZubx/hSLJu9ltmfbiS5IFt0HNw==
Dear Cif-developers,
The CIF core group has not expressed an opinion on the following proposal, so before going ahead with one of the suggested fixes, I would like your opinion as CIF software developers and database curators on the options presented:
The publ_author category has _publ_author.name as the category key, meaning that _publ_author.name can be used to select a unique row of the loop. However, it has been pointed out that _publ_author.name is insufficient as a key for the _publ_author loop, as some authors have the same name (there are apparently 40 entries in the COD with this feature).
Solution (1): Add a further disambiguating data name to _publ_author. The suggestion is that something like "_publ_author.id" could be defined, which would contain an arbitrary code and which would be added to the category key. The lack of this dataname in historical CIFs can be worked around by assuming it has a constant value, and CIF curators can auto-generate it when a situation is encountered with multiple identically-named authors.
Solution (2): Define "_publ_author.id" as the new key of the category that can be auto-generated from each packet. While in a formal sense this makes all current CIFs non-conformant, I can't imagine that it would affect most software, which will continue to work with _publ_author.name.
Please indicate your preference or alternative solutions. Particularly important is the perspective of software authors and database curators who may be impacted.
thanks,
James. (CIF chair/acting core CIF DMG chair)
-- T +61 (02) 9717 9907
F +61 (02) 9717 3145
M +61 (04) 0249 4148
F +61 (02) 9717 3145
M +61 (04) 0249 4148
_______________________________________________ cif-developers mailing list cif-developers@iucr.org http://mailman.iucr.org/cgi-bin/mailman/listinfo/cif-developers
Reply to: [list | sender only]
- Follow-Ups:
- Re: Expanding category key for publ_author.name (Simon Westrip)
- Prev by Date: Announcing a Julia module for reading CIF/mmCIF files and DDLmdictionaries
- Next by Date: Re: Expanding category key for publ_author.name
- Prev by thread: Re: mmCIF specification
- Next by thread: Re: Expanding category key for publ_author.name
- Index(es):