For some reason after migrating to a new computer a scan revealed that all the citations in Mellel weren't matching. I can't think of anything else that was done besides a database rebuilld. (a rebuild doesn't change the unique ID, does it?) This has actually happened to me a few times with this paper and I'm not sure why. I assumed a unique ID never changed.
Anyway, the purpose of this is to request some enhancement for the verify/scan step in Mellel.
1) when I am in the verification window and I verify a citation, can all subsequent citations that are the same also be verified/scanned?
2) If the only conflict in the verification is the unique ID (i.e. the author and date only match one citation) can bookends automatically verify it?
request: update verify and scan
request: update verify and scan
~I swore to myself that if I ever got to walk around the room as manager people would laugh as they saw me coming and applaud as I walked away~
Hi Danny, I don't know why the verify found nonmatches (the unique id never changes). Changes to how verify is implemented in the UI would have to be made in Mellel, not Bookends. As for a ref that matches one reference but not the unique id, no, that's not a match as far as Bookends is concerned. The unique id is essential to ensure the correct result.
Jon
Sonny Software
Jon
Sonny Software
If you export/import a "Bookends" file, the unique id will not change unless there is a conflict with an existing reference in the new database. In that case, of course, a new unique id will be assigned.danzac wrote:Do unique ID's change if citations are imported into a different database?
Jon
Sonny Software
Changed unique IDs after rebuild
I seem to have quite a few corrupt databases. After my last corrupt database, some references changed unique ID and were not recognized by "scanning", which forced me to update all documents that had those references in them.
How can this be prevented?
How can this be prevented?