Store additional author identifiers and affiliations provided by PubMed data during harvests

[mejackreed]

From @darrenleeweber on May 22, 2016 15:17

See https://www.nlm.nih.gov/bsd/licensee/elements_descriptions.html, no. 20.

• <Identifier> was added to <AuthorList> with the 2010 DTD, but was not used until 2013. e.g.

<Identifier Source="ORCID">0000000179841889</Identifier>

• <AffiliationInfo> was added to <AuthorList> with the 2015 DTD. The <AffiliationInfo> envelope element includes <Affliliation> and <Identifier>. e.g.

<AffiliationInfo>
<Affiliation>Harvard Medical School, Boston, Massachusetts</Affiliation>
<Identifier Source=”Ringgold”>123456</Identifier>
</AffiliationInfo>
<AffiliationInfo>
<Affiliation>Program on Regulation, Therapeutics, and Law, Division of Pharmacoepidemiology and Pharmacoeconomics, Department of Medicine, Brigham and Women's Hospital, Boston, Massachusetts</Affiliation>
</AffiliationInfo>
<AffiliationInfo>
<Affiliation>Beth Israel Deaconess Medical</Affiliation>
<Identifier Source=”Ringgold”>678922</Identifier>
</AffiliationInfo>

Copied from original issue: sul-dlss/sul-pub#437

[mejackreed]

From @peetucket on May 23, 2016 20:11

It could be useful to store this information.

Some options could be: a) add fields to the author of the pub_hash data (which is likely to happen anyway), b) add fields to Author or AuthorIdentity, and c) add a new table. I know this was possibly slated for another sprint series down the road.