I've noticed that new tags I'm adding to my Omeka instance wyndhamhistory.net.au (eg. the "Oral History" tag below) aren't showing up on our Omeka Everywhere table.
The tagged items are definitely publicly viewable and the tag(s) in question definitely have items attached.
Any suggestions about what I can try?
Just in addition to this, is there a way to see all of the output from my omeka instance that the OE table is harvesting? I want to try to rule out Omeka as the issue here. If I view my API output (http://wyndhamhistory.net.au/api/items?pretty_print) it's paginated so newer tags don't show up - any suggestions?
Since Flash is single threaded, it does not support asynchronous loading so to prevent runtime latency, only the first page is loaded at initialization. The next release was intended to support pagination but the existing only loads the first page so you will need to increase the number of items per page in your omeka instance to include all items. We are now moving into phase 3 of the Omeka Everywhere project and will be refactoring the table app to no longer require tags as a primary means of searching but will permit paginated browsing of the collection by default and any available tags will simply be a means of filtering the result set.
Ah that makes sense, thanks very much Shaun.
Let me know if you need a beta tester for phase 3 of OE, sounds promising!
Just bumping up this conversation for consideration now that the new phase of OE is well underway? Pagination would be our #1 requirement to actually use the OE table in production.
Pagination is now implicitly supported for items (i.e. scrolling through carousel will automatically load next page) but, you are correct, the tag results are currently being capped at max per page. I have added it to our post-release feature list and we will keep you posted when it has been pushed. Thanks for bringing this to our attention.