- Table of contents
- Data Entry and Manipulation
- Integrated CIDOC CRM
- Interactive Map
- System, Custom and Value Types
- References to other systems
- File Upload
- Network Visualization
- Archaeological Subunits
- Search and Filters
- Users and Groups
This is an overview of implemented features. For upcoming features take a look at our Roadmap.
For more details please take a look at the manual.
Data Entry and Manipulation¶
The web interface provides tools to enter and manipulate data which will be saved in a CIDOC CRM compatible model to a database (PostgreSQL).
It was paid much attention to design a web interface where users don't have to be aware of the underlying data model.
Integrated CIDOC CRM¶
The CIDOC CRM specification was imported to the system, can be browsed and is used to verify link conformity between entities.
Additionally, link combinations can be tested manually e.g when planning model extensions.
A map to enter places with locations is provided (build on Leaflet) and features different view layers, zooming, fullscreen and searching and much more.
PostGIS is used for creating and manipulating spatial data.
It is possible to define multiple points, lines, areas and shapes for locations, detailed information can be found in the Spatial White Paper.
System, Custom and Value Types¶
With this feature the model and user interface (forms) can be adapted for specific research interests.
Already provided system types can be extended.
Additionally, it is possible to add new types e.g. "hair color" for persons. These type hierarchies can be configured to allow single or multiple choices. A type can be used for multiple entities e.g. a hierarchy "importance" for places, actors and groups.
Also value types can be created to add numeric values e.g. weight or material composition of a find.
References to other systems¶
This is an ongoing process. At the moment it is possible to make generic references (e.g. provide an URL for an actor to a Wikipedia entry) and link to GeoNames identifier. The next step will probably be reference links to Wikidata.
Files can be uploaded and linked with entities. It is possible to link one file to multiple entities (e.g. a group picture for many actors) and the other way round. Files are available to download in the original size.
In the admin interface the upload file size limit and allowed extensions can be configured.
With the integration of D3.js it is possible to visualize data as a network graph.
For detailed mapping of archeological finds, e.g. in a cemetery:
- Feature, e.g. a grave
- Stratigraphic Unit, e.g. a coffin or skeleton
- Find, e.g. grave goods
They are used in a strict hierarchy (Place -> Feature -> Stratigraphic Unit -> Find) and can be added and edited in the place view.
Search and Filters¶
To allow quick navigation even in a big data set full-text search can be used.
Additionally, a refined advanced search can be used to filter the results (e.g. only actors and also search in descriptions).
Tables and tree views can have many entries and have a full-text filter for convenience.
The map provides a search field for a GeoNames search.
A CSV export for single tables and a SQL export (pg_dump) are implemented in the admin interface.
A basic import for e.g. a list of persons (name and description) with a CSV or an Excel file.
Users and Groups¶
Users and Groups are used to grant different access levels, more information is available at the manual
Multiple languages for the user interface are implemented with gettext.
At the moment English and German are implemented but it can easily be extended if translations for other languages are available.
If an entry has been modified after the update form was opened, an error message is displayed.
- Only the main entities are being checked on update (source, event, actor, place, reference). It is still possible that e.g. a type name accidentally gets overwritten.
- Some advanced form elements don't behave like expected after an overwrite error e.g. jsTree with multiple options isn't prefilled with chosen options. This shouldn't be a big issue, since the entry can't be saved in this state anyway.
This feature enables managers and admins to send newsletters. An editable receiver list with users which have opted in is shown. Newsletters will contain an unsubscribe link.
Bookmarks are user specific and can be used to e.g. mark entries which need further editing. Already bookmarked entities are shown on the start page after login.