1 Reply Latest reply on Mar 2, 2018 12:25 PM by D3UH

    ADE: Various issues with library (limited time use) editions


      Hi!  We are in the midst of a college library pilot of a large number of books in ADE.  There are a number of immediate program limitations that I have encountered.


      The system is set up so that a patron can take a book out for a 24 hour or 7 day loan period.  There are unilmiited numbers of simultaneous users.  The files have a limit on the copy and print portions.


      The issues i have encountered thus far:


      1. Sloppy / wasteful file storage and duplication: Every time a copy is checked out, even it is the same book, a new "urllink.acsm" file is created in the downloads directory, and when that file is clicked (why doesn't the Adobe Digital Reader automatically scan for new ones by the way when it opens?) a new copy of BOOKNAME.pdf is created in the Documents/Digital Editions directiory.  Even in the first week that I have been experimenting with the system, for example, I have six duplicate files in the "Digital Editions" directory.  All the older ones are just expired copies of an identical book.

        1. Suggestion: The system should overwrite older copies of an identical book, not create an identical file with 0001, 0002, etc. appended to the file name.

      2. Bookmarks not saved after a book expires and is re-checked out: If I download a book, read it, make annotations, and then my loan expires, I have to recheck out the book.  My annotations are all lost!  This is a huge limitation for any book borrowing system that is going to work for the academic / teaching market.  What is frustrating is that I discovered how easy it is to trick the system.  Your annoations are saved in a file called "BOOKNAME.annot" in the "Documents/Digital Edictions/Annotations" directory (on a Mac).  When the book loan expires and you re-check it out, the system will create a NEW "BOOKNAME.annot" file, overwriting the old one.

        The workwaround is simple--before you open up the new copy of the book, rename the old file (e.g. BOOKNAME.annot.copy).  Now restart the program and make a single annotation in the new copy.  The program will overwrite the previous BOOKNAME.annot.  Close the program, Then BEFORE OPENING the reader again, delete BOOKNAME.annot and rename BOOKNAME.annot.copy to BOOKNAME.annot. 

        When you open the book again, Voila!, the "old" bookmarks have been restored.

        I have no idea why the program would ever be designed this way.  I have no idea why an IDENTICALLY named file of annotations is not recognized by the system, but when you delete a file and rename a copy to the original name, suddenly the system recognizes it.

        1. Suggestion; FIX THIS!  Annotations that are tied to a book title should remain tied to that book title, no matter how many times you have to re-check out the book.  Otherwise your system is completely unusable as a library check out / return reader.

        2. Suggestion 2: ALLOW BOOKMARKS/ANNOTATIONS TO BE PRINTED!   This is part of every E-Book reader out there.