Skip to content
Pre-release

@jamiefolsom jamiefolsom released this Feb 18, 2019 · 4 commits to master since this release

Development Release v0.1.0

This is a PHP Module to be installed Omeka S, to be used with the Neatline "Single Page Application" (SPA), a new front end for Neatline written in javascript. Together, they implement a new version of Neatline for Omeka S.

This module provides authentication and data persistence through a REST API, which the Neatline SPA uses to provide familiar administrative and end-user interfaces to Neatline. This version of Neatline is a complete rewrite, and is compatible only with Omeka S.

Release Overview

This release is not suitable for production use, and the API is subject to change at any time.

This release is intended to support ongoing development and testing, and should not be used for production purposes. Some features are missing, and it may contain bugs. Please open an issue if you encounter one.

Future development releases will be similarly numbered, following the Semantic Versioning Specification, until a production-ready release is made, which will be tagged v1.0.0. Exact timing of that release has yet to be determined.

Features implemented

  • Basic User Authentication via JWT
  • Exhibit creation and editing
  • Record creation and editing
  • Creation of map features on records

Known issues

  • All exhibits are visible to all logged-in administrators
  • Records cannot be created from Omeka items
  • Some record styling options are not available
  • User interface design is very basic
  • Access the Neatline user interface by adding /neatline to the end of the public site URL

Other notes

This version of Neatline is designed to be served either from within Omeka (similarly to how Neatline 2.6 works with Omeka Classic), or as a stand alone, "Single Page Application" ("SPA"), which persists data to an Omeka (or other) backend through a REST API. This release is focused on the classic, Omeka-served approach, but future releases will introduce more support and documentation for stand-alone installations.

This release does not contain a zipped installer; for development purposes, deployment is done using git submodules, and is documented here. A future release will include a build of the module including the SPA, which can be installed into Omeka S as usual.

We expect many users to serve Neatline as they have in the past, directly within an Omeka S installation, and we will release a module which makes that as easy as it has been in the past. A few differences will be readily evident.

Apart from the installation, configuration and upgrade interface, which will be handled within the Omeka admin interface as before, all Neatline exhibit and record administration will occur within the front end application. Exhibit creation, editing, and management are now concerns of the "Neatline SPA".

The UI for this release is not polished; the next release will introduce a cleaned up and improved user interface.

Assets 2
You can’t perform that action at this time.