Goodreads Librarians Group discussion
Archived
>
combine page will now be paginated
date
newest »

message 1:
by
Otis
(new)
Jul 17, 2009 11:12AM

reply
|
flag

Edited to add: I suppose a workaround would be to edit the title of the nonromanized book to include the romanized title, filter on that, combine the editions, and then edit the title back. Extra work, but probably not required very often, so I'd call that acceptable. (We can add it to the librarian's manual!)
That's a good notion for a workaround, Cait.
And yeah, some of the more prolific authors have combine pages that take aeons to load; this sounds like a very reasonable way to avoid that problem. Thanks for the heads-up, Otis!
And yeah, some of the more prolific authors have combine pages that take aeons to load; this sounds like a very reasonable way to avoid that problem. Thanks for the heads-up, Otis!



I would definitely be in favour of an adjustment like that, as it's impossible to combine books that are at different pages and, in case of foreign-language translations, search doesn't help either. I've just encountered this problem today, when adding some Isaac Asimov's books' translation editions and I would be seriously grateful if something could be done about it.



This way, the 500 limit is there and for most cases works really well, but if you want to join across pages you need to use the work around of adding common text, searching, combining, deleting the added common text.
When I shop, there is often a drop down at the bottom of the page to ask how many items per page I want to view. Perhaps somewhere on the combine page, there could be an option to "show all".
(Does this go here or in the Feedback group?)


I know, I just thought that may be it could be there just as an option. (In case of emergencies!)
Overall,the split combine page works really well - it absolutely speeds things up, it's just that the join across pages is a little clunky ...
Thanks.


Then I could search for "Temps" or "Time" so I could combine a French and English version of the same work (as an example). or even traditional wildcards (* %) from DOS (see how old I am!).
Is this clear, or should I keep writing ....

Shomeret


I'm working on a solution, but it requires a re-index of our search server and it's being finicky - stay tuned.

http://www.youtube.com/watch?v=vube-Z...
Shomeret

Boolean Search.
Many catalogs are post boolean because boolean can be very limiting as they are determined by indexing and that could in term is determined by language use( which may or may not be standardized).