search

oaregithub / oare_mono

1 stars 0 forks source link

Fix Zotero referents #1387

Closed edstratford closed 2 years ago

edstratford commented 2 years ago

Some zotero keys are failing.

This could be just plain bad errors, or the result of the Zotero being poorly organized (between three different accounts of mine), and also has the possibility of being due to the need to eliminate duplicate entries in Zotero. In this last case, two or more entries for the same book/article in Zotero are the result of a previous project with students that were not done well. Cleanup for that is still ongoing. When I merge some of the entries, if I used the key for an entry that is deleted in the process, that will require the key in SQL to be updated. This means that the consolidation will go much slower, unless I create a list of merged keys and the keys they should be updated to. However, still need to figure out how to develop that with the Zotero API. Merging happens on their front end and does not report the Zotero keys...

edstratford commented 2 years ago

@hbludworth I only need from you a way to know if I've fixed the data from your end. For example, I found some errors for 5 texts come from a book abbreviated as VS 26 (zotkey 4XB2SCFJ), and I think I fixed them, but I don't know how to tell if it is fixed. Nothing appears with the bibliography on the front end site yet (that I can see). For example VS 26 19, VS 26 20, VS 26 29, VS 26 57, VS 26 1, VS 26 93 -- all of these had the wrong object_uuid in item_properties, but now have the correct one, so they should 'work'. Is there somewhere I can check it to make sure I have resolved it? -- there may be something further upstream that is still failing.

edstratford commented 2 years ago

@hbludworth -- progress. I had been getting zot item keys from a group inside my user account, and item keys in zotero are not the same for items in my core user db and the group db, so the majority of these keys were not for the right group. I have updated that in the SQL db, so that it points to the right db within zotero.

I am sure that there will be more cleaning up, but I think that this will dramatically reduce the number of unresolved API requests to zotero for now.

edstratford commented 2 years ago

Identified a few duplicates in SQL and missing / extra entries in both sets. SQL is now aligned with Zotero.