I added the entire Presues digital library to my priority list. Is there any way to clear all priorities at one time instead of individually right clicking and choosing +remoove from list "
Hi Mike - and welcome to the forums.
I don't believe you can remove more than one entry at a time.
The Perseus resources should have appeared in the Prioritize lists as varying size sets and each set can be removed in one go but - outside of that - I am afraid it is one at a time.
Graham
Yet another limitation of the current Library implementation. I'm just sayin' [6]
Yet another limitation of the current Library implementation. I'm just sayin'
Except that they were manually added to the list one at a time, whether for a series or an individual resource. Not the same issue as unwanted resources.
Dave,
Actually I added all 1008 at the same time. I think it was only 2 clicks of the mouse.
Since you mentioned it is there a way to get rid of unwanted resources.
Thanks Mike
Ouch! I was hoping you wouldn't say that - now you know better[:)]
Yes. See http://wiki.logos.com/Hiding_Books and notice the Tip for hiding 10 at a time!
If you are thinking you don't need Perseus you can request Logos to revoke your licence, which would be a convenient way of getting them off the Prioritize list. But if you choose to Hide them they should also be removed from that list.
Thanks Dave and everyone. I appreciate the help.
"Because Salvation Is No Illusion"
Mike
Actually, can't you simply un-prioritize Perseus by placing other resources ABOVE it???
Very logical if the "others" are less than 1008 in total.
Dave, I don't understand. I thought 1008 referred to Perseus. But even then, batch highlighting Perseus again and dragging it BELOW all others, wouldn't it work as well. There are many ways to accomplish the same thing.
Dave, I don't understand. I thought 1008 referred to Perseus.
Sorry, I meant that moving 50 or 200 "other" resources was better than moving 1008 Perseus resources in the List.
But even then, batch highlighting Perseus again and dragging it BELOW all others, wouldn't it work as well.
You have to select them one at a time! Back to square one.
I know the prioritization list is stored somewhere. Perhaps in the Library Catalog database. I wonder what else would be lost by eliminating the correct database and forcing Logos to rebuild it? You'd certainly have to reprioritize your library but that might be a lot faster than deleting 1000 of them one at a time. It all depends on what else would be lost.
Dave, do you know which database this is in and what else one might lose by deleting it?
If you deleted the file it would almost certainly sync back. If you want to try it it's %localappdata%\Logos4\Documents\{random}\KeyLinkManager\KeyLinkSyncManager.db
It would be possible to hack that file to achieve a mass delete, but I'm not sure that's wise.
<edit>There's also %localappdata%\Logos4\Data\{random}\KeyLinkManager\keylinkmanager.db which contains essentially the same information. You'd need to edit/delete both files, I think.</edit>
If you deleted the file it would almost certainly sync back.
Then the approach would be to do the delete and rebuild off-line and then go back on-line and let Logos sync up the new list. Maybe??
But even then, batch highlighting Perseus again and dragging it BELOW all others, wouldn't it work as well. You have to select them one at a time! Back to square one.
No, you misunderstood me. Selecting entire Perseus in the Library, not in the prioritization list can be done with a couple of clicks. Then "move" it to the prioritized list (which already has it) but to the bottom of the list - it is confirmed to "down-prioritize" for the lack of better term.
WE NEED A BETTER LIBRARY MANAGEMENT SYSTEM, PLEASE[:'(]
I considered that, but have you tried it?
If you deleted the file it would almost certainly sync back. Then the approach would be to do the delete and rebuild off-line and then go back on-line and let Logos sync up the new list. Maybe??
I think the lack of delete transactions would cause a re-population..
No, you misunderstood me. Selecting entire Perseus in the Library, not in the prioritization list can be done with a couple of clicks. Then "move" it to the prioritized list (which already has it) but to the bottom of the list - it is confirmed to "down-prioritize" for the lack of better term. I considered that, but have you tried it?
I did not try it with Perseus, but YES, I successfully did it with other resources.
Did you try it with the same resources already prioritised (using batch select from Library)?
If you deleted the file it would almost certainly sync back. Then the approach would be to do the delete and rebuild off-line and then go back on-line and let Logos sync up the new list. Maybe?? I think the lack of delete transactions would cause a re-population..
Let me say this isn't the way to go!
With one machine, the original transactions did NOT sync back and the list I built offline was unaffected. When it sync'd with my second v4.5 installation NOTHING was deleted and I had duplicate entries from resources in both lists and the extra entries (Perseus if you like ) sync'd back to the first machine (where they had been removed offline!).
That would imply I should have deleted the Sync database from the second installation. Anybody care to guess what would happen thereafter?
I did not try it with Perseus, but YES, I successfully did it with other resources. Did you try it with the same resources already prioritised (using batch select from Library)?
Look, how many times do I need to say: "yes, I fully vetted my method by first "prioritizing" unnecessary resources on the top, then batch selecting them in the Library and "prioritizing them" at the bottom of the prioritization list." YES! I have! I have done it!
Still don't believe me? I am not going to do screenshots now, but maybe later. Why don't you try this yourself with say, 5 resources. This method is by far the simplest one to date.
And Dave, to answer your question, YES![;)]
That would imply I should have deleted the Sync database from the second installation.
You're a brave man to try it.
I can see that having machine with an intact db would mess this up. I just wonder how the sync system works. How does it decide which machine to copy changes from?
Perhaps taking all machines offline and deleting their files when you do this, altering one, bringing it online and syncing, then bringing the others online would get the desired result. Perhaps not.
Hope the mess I helped create isn't too hard to clean up.
I have tried it but nothing changes from the right click menu. If you try dragging the multi-selection the desired affect occurs for only one resource. That's why I'm keen to know exactly how you achieved it.
I was prepared for that. I deleted the small amount of duplicates and sync completed the restoration!
Macro Express Pro, record a deletion of 10, then replay macro as often as needed.
