-
Neatline currently only provides a very limited set of fields for importing Omeka items, and leaves off quite a few fields that would be useful, like importing items added by a particular user. I have…
-
If you install a custom CSS theme for your Scripto project to match the theme you're using for your Omeka site (let's say the site is called "writings"), most pages turn out as expected: for example, …
-
I'm trying to upgrade an existing installation of Omeka 2 to Omeka S, but every time I run this script, it fails out shortly after upgrading the users and as soon as it starts the site upgrade. The …
-
The [convert-data-types](https://github.com/omeka/omeka-s/pull/2231) branch adds the ability to batch-convert resource values from one data type to another data type. To test this, batch edit a few it…
-
Hi,
Many thanks for your work on the plugin. I've a question regarding indexing TEI xml files (or their text node contents) attached to Omeka items. I came across [an old Scholar's Lab post from 2010…
-
What I did:
- I used the base install of madoc-platform, running `madoc init` and `madoc start` with no changes to the config
- I logged as the admin user
- I selected `Create IIIF Manifest` from t…
-
If you delete users from Omeka S without first removing them from their projects, it breaks the add/remove users functionality on that project such that you can no longer add or remove new users for t…
-
-
This is a question for @jeremyboggs for now: what should the zipfile, the module be called, how should it be versioned, and how should we handle releases that depend on various versions of Omeka S?
-
We should at a minimum, document that as a known issue, but as soon as possible, address it, so that neatline does work when run at any subdirectory route.