Testing: Suggest Omeka values - Githubissues

omeka-s-modules / ValueSuggest

GNU General Public License v3.0

10 stars 13 forks source link

Testing: Suggest Omeka values #71

Closed jimsafley closed 1 year ago

jimsafley commented 1 year ago

The omeka-suggesters branch adds three data types that suggest values that already exist in the working Omeka installation:

Omeka: Property: suggest values using the current value's property
Omeka: Property / Resource template: suggest values using the current value's property and current resource's template
Omeka: Property / Resource class: suggest values using the current value's property and current resource's class

To test this, it's best to have a lot of richly described items. You could use the Omeka S Item Importer module to import from any number of Omeka S installations. When editing a resource template, add each new data type to properties that are often used to categorically describe resources, such as dcterms:type or dcterms:subject. Then, add an item, select the resource template you edited, and start typing values that you know exist for that property/template/class combination. It should work for both Text and URI types. It should respect the current language.

allanaaa commented 1 year ago

I'm not getting anything. After the third character is typed, my cursor changes to a spinning wheel for a second (and for every character after), but nothing is being suggested.

jimsafley commented 1 year ago

Is there an error in your JS console? Are you sure there's an already existing Publisher value that begins with "pai"?

allanaaa commented 1 year ago

Yep. "edinburgh" and "paisley" should get it going for publishers, "bunyan" for creator.

All I've got is "wrong event specified: touchleave DomEvent.Pointer.js:36:10" for errors.

jimsafley commented 1 year ago

What data type of the three are you using for that property?

allanaaa commented 1 year ago

I set all of them to "Omeka property" for the widest range. I have done some template and class labelling of my items but I haven't used those data types yet.

allanaaa commented 1 year ago

Hrm, it's working now! And it's positively beautiful. pai

I did go and turn off a bunch of other modules as part of the troubleshooting, not clear if that was part of it or if it just needed time to index behind the scenes?

jimsafley commented 1 year ago

It is strange. The only reason it should behave that way is if you're logged in as an author and the source item is set to private. Otherwise, I'm at a loss. There's no indexing. Try activating modules one at a time to see if one breaks this feature.

allanaaa commented 1 year ago

All modules are active and everything seems to be fine.