Suggest: Interlisp.github.io release should auto-update data/bibliography.json #1327
Replies: 3 comments
-
|
Zotero offers no version management (does it? Asking @AbeJellinek ) so having backups of at least the bibliographic material seems like a good idea. The json file doesn't keep attachments, so not ideal. There might be a credential problem running update from a script. |
Beta Was this translation helpful? Give feedback.
-
|
There's probably little value in keeping old versions, if we assume Zotero will be around and we can continue to pull a copy of the bibliography. I have written a GItHub Action that uses our existing script. I also have a script written in @masinter Zotero does provide the ability to figure out if the bibliography has been updated. The REST interface command: returns a bunch of information on the Interlisp bibliography, the meta entry, holds the key information, the |
Beta Was this translation helpful? Give feedback.
-
|
The website at presents checks Zotero daily and updates the bibliography entries if the information on Zotero has changed. The Github Action, In addition, the results are cached and on subsequent builds, if there are no changes to the bibliography, we do not rebuild that portion of the system. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
The file
data/bibliography.jsonis just a file in the repository and it must be updated as part of a git commit.I suggest that the script to update that file, using API access to the Zotero database, be invoked as part of a release "build" of the website. (I.e.,
scripts/update_bibliography.sh).Is there some specific value to keeping versions of the
bibliography.jsonfile in the repository?Beta Was this translation helpful? Give feedback.
All reactions