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

Publication 'Publisher' as a related Contributor #294

Closed
justgo129 opened this issue Mar 24, 2016 · 3 comments
Closed

Publication 'Publisher' as a related Contributor #294

justgo129 opened this issue Mar 24, 2016 · 3 comments

Comments

@justgo129
Copy link
Contributor

justgo129 commented Mar 24, 2016

Migrate the values of the publication "publisher" field into that for the "publisher" as a "contributor" field for books (i.e., move value of "publisher" in "books" to that of "publisher" in "contributors"). Ignore where this has been done automatically.

Note: the subject of the level of granularity for publishers and the addressing of the various changes in the publisher market (e.g. Wiley or Elsevier has many divisions) is topic for discussion.

@lomky lomky changed the title Make "publisher" searchable Publication 'Publisher' as a related Contributor Jul 13, 2016
@rewolfe
Copy link
Member

rewolfe commented Jul 13, 2016

Example of the publisher linked through a relationship (the way we would like this to be): http://data.globalchange.gov/book/03826610-743d-4e51-a08e-8fe8d294fa83

@lomky
Copy link
Collaborator

lomky commented Jul 13, 2016

So, instead of having the publisher in the column of the publication table, we want the publisher to exist as a contributor and relate it properly.

Good candidate for a scriptable fix.

We want to remove the publisher field from the table after migration is complete.

@lomky
Copy link
Collaborator

lomky commented Dec 11, 2017

This is done! #548 #549 #553

@lomky lomky closed this as completed Dec 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants