Goodreads Librarians Group discussion

167 views
Additions to Librarian Manual > Suggested addition: Quotes don't follow books when book author is updated

Comments Showing 1-9 of 9 (9 new)    post a comment »
dateDown arrow    newest »

message 1: by Keith (last edited Jul 06, 2018 04:52PM) (new)

Keith (kgf0) | 354 comments In the section on Editing author names, I suggest the following addition, since this function does not appear to be noted elsewhere:

Cleaning Quotes When Editing Authors

When editing the author of a book because the work is attached to the wrong author—as must often be done for books by authors who have been disambiguated from other authors of the same name—please first check the work to be edited for attached quotes. These quotes will not be moved automatically to the profile of the author to which the book will be transferred, and therefore need to be edited separately.

You can request assistance with editing such quotes in the appropriate folder of the Goodreads Librarians Group if needed.

Fine tuning of this suggested language is welcomed.


Christmas Carol She's So Novel꧁꧂  | 5875 comments Keith wrote: "In the section on Editing author names, I suggest the following addition, since this function does not appear to be noted elsewhere:

Cleaning Quotes When Editing Authors

When editing the author o..."


+ 1. It never occurred to me to check that.


message 3: by Elizabeth (Alaska) (last edited Jul 06, 2018 05:10PM) (new)

Elizabeth (Alaska) | 7152 comments I have never used the quote feature, either as a user or as a librarian. (I do have one quote on my profile, but I think I just typed it in.) I don't even know where to look for it. And if this is going to be a requirement, either I'll be doing a lot less librarian work, or my librarian status will be rescinded.


message 4: by Emy (new)

Emy (emypt) | 5038 comments I wouldn't worry too much - it's only really an issue when doing disambiguation work. When you disambiguate a title any associated quotes don't follow the book move, so we have to move them manually, or they stay on the 1^ profile. I do a fair bit of disambiguation so I do need to stay on top of this, but if it's not something you do regularly, it's not something you'd need to worry about! It's only a task I would undertake when also working on a disambiguation - at the same time as moving the book records.

Keith, I do think this is worth noting in the manual, but as Elizabeth's reaction shows, the wording needs to be a touch less dogmatic sounding. I'm falling asleep right now so I won't suggest anything as it'd probably be nonsense!


message 5: by rivka, Librarian Moderator (new)

rivka | 45480 comments Mod
It certainly would be a suggested additional step, not a required one.


Elizabeth (Alaska) | 7152 comments Emy wrote: "When you disambiguate a title any associated quotes don't follow the book move, so we have to move them manually, or they stay on the 1^ profile. "

I disambiguate occasionally - have done more so in the last few months - only public domain authors, I think. I have also corrected an author within a book, rather than disambiguate on the edit author page. I move up/down authors regularly. But I still wouldn't know where to see if there are any quotes.

This sounds to me as if it should be done on the developer/programming side.


message 7: by Emy (new)

Emy (emypt) | 5038 comments I would agree with that Elizabeth. My personal preference would be if it could be coded to attach the quote to the book rather than the author, but I understand that may not be possible. That sort of thing would need to go to Feedback anyway I guess.


message 8: by Keith (new)

Keith (kgf0) | 354 comments Emy wrote: "…if it could be coded to attach the quote to the book rather than the author…."

That would produce a problem for books with multiple authors (e.g., a collection of essays or short stories). Proper attribution requires both a who and a where.


message 9: by Keith (new)

Keith (kgf0) | 354 comments Elizabeth (Alaska) wrote: "This sounds to me as if it should be done on the developer/programming side."

I agree that this would be vastly preferred by virtually all GR Librarians, and that it is the "right" way to do it. And given the list of such feature/enhancement requests of higher priority that have gone ignored for years, I feel confident that it will never, ever happen. There's simply no business justification for it (i.e., there is no way that such a change can have a positive impact on revenue, and it will cost money to implement).


back to top