Ulysses tagging

RRD · January 2016

The Noet edition of Ulysses which I purchased on sale is described as: "fully indexed and tagged allowing for near instant search results. Use the dictionary lookup tool to dig deeper into Joyce's novel use of English words. The books are linked with the rest of your library, allowing you to look up literary and historical allusions with a click." The book is described as having 470 pages.

I tried to set up a reading plan and discovered that there are no pages numbers. As far as I can tell the only tagging is for the title. None of the other tagging, indexing, or linking appears to be present.

Any suggestions?

NB.Mick · January 2016

I tried to set up a reading plan and discovered that there are no pages numbers. As far as I can tell the only tagging is for the title. None of the other tagging, indexing, or linking appears to be present.

Noet has tagged the three chapter headings that come up in the ToC (I, II, III without further text) as such. When I tried to set up an automated reading plan over a year for that book (in Logos 6, RC 2), I found that something seems to throw the algorithm off, since it doesn't build breaks within those long chapters, resulting in long periods without a reading - Title page is today, Chapter I on July 24th. To me, this seems a bug in the Logos software.

I agree that with such a book, page numbers might be helpful to cite it.

The book is indexed, thus you can search for it's content, and it will come up when you search accross all your library for words contained in this book. E.g., if I search my library for "stairhead", I'll find that Ulysses is one of four resources I own that use this word (one being the Concise Oxford English Dictionary).

The dictionary lookup you describe from the product page will work, too - even for different laguages as the text is tagged accordingly (thus double-clicking "stairhead" opens the COED for me, while clicking "introibo" opens an analytical Latin dictionary, telling me it's first person singular future of a word that means "enter"

Regarding linking to the rest of your library: since the author did not use references and such (after all, this is a work of fiction), the looking up of things will work mainly through the right-click menu which brings up various search options and the dictionary lookup again (among other features).

Any suggestions?

Regarding the reading plan?

You could build a Custom Reading Plan from selections, but this would be a considerable amount of manual labor.

RRD · January 2016

https://community.logos.com/discussion/comment/798603#Comment_798603

Thank you for your helpful response.

Despite having more than 7,000 resources in my library, I am now convinced that to achieve full functionality, as described, will require additional resources.

Also, despite already having numerous dictionaries, I purchased the Collins English Dictionary (unabridged). There was an immediate improvement in the hit rate on selected words. I found very few currently available resources to address Joyce's numerous musical, literary, philosophical, theological, and historical references and allusions. There are, however, several likely candidates on Pre-Pub and Community Pricing.

I contacted Customer Service and appreciate the assistance provided, including use of the remote option. The allusions issue was referred to the developer team and I will be contacted by email.

Many fictional works in Noet have almost identical descriptions regarding how the full tagging, indexing, and linking provide in-depth search options. It would be helpful to know the specific additional recommended resources needed to make for consistently successful searches. I'll make a suggestion in the forums.

Thank you, again!

JAL · January 2016

https://community.logos.com/discussion/comment/798646#Comment_798646

I found very few currently available resources to address Joyce's numerous musical, literary, philosophical, theological, and historical references and allusions.

From https://community.logos.com/forums/p/99148/722751.aspx#722751: