Note that Mozilla has largely switch to Fluent for localization, but Zotero 7 is currently still using .properties/.dtd files. Plugin authors may wish to investigate Fluent for localization of their plugins.
https://www.zotero.org/support/dev/zotero_7_for_developers

Maybe worth looking into.

Currently nothing happens when clicking this. On Zotero 7 the text is empty.

If the LIDIA panel is built directly after startup, this fails in Zotero 7 because the window is not yet ready.

The line where it fails is:
const tabbox = tabContainer.querySelector("tabbox");

Fix this, perhaps by waiting for a certain amount of time if it fails and try again?

Currently annotations are not automatically saved. When switching to another annotation without explicitly clicking the save button, the changes are discarded. This is not userfriendly and counter-intuitive.

Saving each time the user presses a key is probably too expensive or it may cause synchronization issues, but possible solutions are:

• Saving each time a user selects a different field
• Saving every couple of seconds
• Saving just before activating a different annotation
• Warning the user before activating a different annotation if there are unsaved changes

In case of automatic saving, it is probably necessary to give the user feedback about the saving status, to avoid data loss if the user exits the application.

As spotted by @bbonf

Currently we use the Zotero key for cross-references to annotations, but this is problematic because Zotero assigns a different ID when moving items from the local library to a group library. We can solve this by giving all LIDIA annotations a LIDIA-specific unique annotation ID. We may use the uuid npm package for unique IDs.

Since users have already been adding cross-references, we need a transition mechanism.

Relations to other arguments currently only store the annotation's zoteroKey which identifies the publiation or pdf, not the annotation.

Figure out if there's a global id we can use (shared also when syncing via groups), or if it should be zoteroKey + argument name/id.

Small changes needed in the UI that can quickly be implemented:

• Lack of space after Page start / Page end (as noted by @bbonf)
• Inconsistent aligning of terms and lack of colons

Needed for Zotero 7.

Currently the LIDIA tab (= the tab button itself) and the LIDIA panel are reused for all documents, but this is not how it is supposed to be: every document should have their own. This would solve the following issues:

• Right now we force-activate the LIDIA tab every time the user switches documents, but this does not work on Zotero 7 for some reason. When this activation does not happen, the tab button remains selected (because it is the same XUL element, which is still active), but the panel does not show.
• Making separate panels for each document allows the user to keep working in an annotation when looking something up in a different document

It should be possible to select and copy (part of) the argument text (i.e. the annotation's selected text), either in the annotations sidebar or the annotation form on the right.

http://linguistics-ontology.org/info/about - server seems down at the moment :(

Read bibliographic items and their annotations from Zotero's Web API to provide a searchable database of annotations (standard Django app).

For example, in a LIDIA tab in the library view

Disable input fields for annotations by other users (read-only).

Using the ISO 639-3 or an extension of this. Ideally the user can select from all entries in an efficient way (e.g. autocomplete).

A field prepopulated with annotation-ids (labeled with argument name) from the Zotero group library, and an option to specify the type of relation (confirms, contradicts, etc.; Jan will provide a list).

Argument language and linguistic level (subfield) should receive default values per article.

We'll probably need to store this in the Zotero item. Some plugins use key: value in Zotero's extra field, maybe we can use that and provide it to the plugin?

Also: give feedback to the user that an annotation cannot be edited, even though it is a valid LIDIA annotation (in case it is an annotation by somebody else)

Clicking them does not do anything. Otherwise they work correctly, and changing is possible using the arrow keys.

At the moment the behaviour is not well managed in case an annotation is deleted that:

• Is linked to from a different annotation
• Is continued in a different annotation

Especially the second case may lead to confusion, because automatically the annotation before the deleted one will be marked as the continued annotation.

Check if it is possible to act on deletion of an annotation, and if not, handle it correctly when a form is opened.

Use itemAnnotations.comment field using field markers, or find another mechanism for custom data. Data must be synchronized with Zotero servers.

Outfactor everything that belongs to the data model to a separate class

A recent Zotero 7 beta release removed item pane tabs, so our annotation form no longer shows up. We'll need to wait for the new API to add the form to the new vertical sections instead:

item-pane tabs have been replaced with collapsible vertical sections. We'll be introducing a new API soon that lets plugins create sections there. You'll need an icon that will appear for your section in the navigation bar on the side.
https://groups.google.com/g/zotero-dev/c/A-_e78q_W5o

Notes

• Installing: Zotero: Tools > Addons > Install Add-on From File.
• If you had PDFs open in Zotero, reopen them to allow loading the LIDIA extension.
• Toggle both the left and right sidebars (left: annotations, right: contains a tab LIDIA with the form).
  (Add screenshot showing the buttons and example annotation list + form?)
• To activate the LIDIA form for an annotation, click the annotation in the left sidebar.
• Converting PDF annotations to Zotero annotations: ...

Group use (later):

• If you add a publication from your personal library to a group library, the attachment item (pdf) will also be the same (same key). If you want to have the publication separately in your own library (e.g. with your own annotations separate from LIDIA's), it may be easiest to create a duplicate of the publication and attachment.
• If you select an annotation made by someone else in the group, you will see the form, but cannot edit it. #15

Display a link to the entry for vocabulary terms (Lexicon of Linguistics term, Clarin concept registry item from a subset of included concepts). Low priority.

Using React component in Zotero Plugin?

Minimal example.

Using JSX

text: The esbuild loader for this file is currently set to "js" but it must be set to "jsx" to be able to parse JSX syntax. You can use "loader: { '.js': 'jsx' }" to do that.

In build.mjs, add: loader: { '.js': 'jsx' },

Using NPM packages

Some Zotero plugin authors are using require and note that in that case the module should be declared as external in order to be left alone by esbuild.

I'm using esbuild these days, and I have found you can declare modules as external, and it will just leave those require's as-is. src

It looks like annotations with "Annotation is continuation of previous argument" are not saved.

• Create .xpi addon upon releasing a new version
• Update the update manifest
  • Place in public location
  • Test

Creating the xpi and update manifest can probably be done via Github Actions workflow. Not sure if there's a way to upload it to dhstatic though, maybe we should just make the repo public and use Github for all of it.

A boolean field which indicates that a text selection belongs to the annotation started on a preceding page.

If checked, the rest of the form should be disabled.

External annotations are read-only by default — indicated by a lock icon — but you can transfer them into Zotero by selecting File → “Import Annotations…” from within the PDF reader, after which they'll be fully editable. The annotations are removed from the PDF to avoid conflicts and duplicates.
https://www.zotero.org/support/kb/annotations_in_database

Make sure we use copies of the annotated PDFs in case someting happens to the Zotero annotations.

Try to also import the annotation text into the short description field.

Wishlist: present long hierarchical lists of GOLD terms as hierarchical select elements.

Search for a suitable library. Someting like https://github.com/dowjones/react-dropdown-tree-select?

We currently use key = value as the text format. We picked this since it's a bit easier to read/edit by hand, but we could consider using JSON or YAML. Especially now that we probably need to be able to store multiple subfield+term combinations per argument.

For a user the plugin appears to be installed correctly, but the Lidia panel remains disabled when activating an annotation. Possibly related to the PDF being synchronized via Zotero.

[JavaScript Error: "Error: getAnnotations() can only be called on file attachments" {file: "chrome://zotero/content/xpcom/data/item.js" line: 3945}] [JavaScript Error: "Error: getAnnotations() can only be called on file attachments" {file: "chrome://zotero/content/xpcom/data/item.js" line: 3945}]

Serializing and deserializing does not support these now. Add support or don't allow multiline at all.

• Add article term: subfield + lexicon term
• Add custom article term: subfield + custom term
• Ability to add multiple combinations, for both article term and lexicon terms.
• Argument name should become the human readable label for the annotation ID. Also display the annotation ID in the form?

Following Setting Up a Plugin Development Environment:

• Create a new Zotero profile via zotero --ProfileManager(here: "Develop").
• Configure a custom data directory for the new profile.
• Start the new profile: zotero -P Develop; quit.
• git clone [email protected]:UUDigitalHumanitieslab/lidia-zotero.git /path/to/Projects/LIDIA/lidia-zotero
• git checkout feature/example-make-it-red # src-1.2 = Bootstrapped plugin for Zotero 6 and 7
• mkdir $HOME/.zotero/zotero/Develop/extensions
• echo "/absolute/path/to/Projects/LIDIA/lidia-zotero" > $HOME/.zotero/zotero/Develop/extensions/[email protected]
• sed -i '/.*extensions\.lastAppBuildId.*/d' $HOME/.zotero/zotero/Develop/prefs.js
sed -i '/.*extensions\.lastAppVersion.*/d' $HOME/.zotero/zotero/Develop/prefs.js
• zotero -P Develop # The plugin is now enabled from the source directory
• Make changes and restart Zotero...
• zotero -P Develop -purgecaches -ZoteroDebugText -jsconsole