-

On the index page already entered entities are listed in a Table.

+

At the index page already entered entities are listed in a Table.

    -

  • Click on the + button to enter a new one.

    • -

  • Click on the name of an entry in the list to access the detail view.

    • -

  • To edit or delete an entry click on the Edit button in the detail view.

    • +

  • Click on the + button to enter a new one

    • +

  • Click on the name of an entry in the list to access the detail view

    • +

  • To edit or delete an entry, click on the Edit button in the detail +view.

diff --git a/openatlas/static/manual/entity/place.html b/openatlas/static/manual/entity/place.html index 0f1df82b5..3b1d41578 100644 --- a/openatlas/static/manual/entity/place.html +++ b/openatlas/static/manual/entity/place.html @@ -112,13 +112,14 @@

Place

CIDOC documentation: E18 Physical Thing and E53 Place

-

A place can be e.g. a continent, a city or a graveyard. +

A place can be e.g. a continent, a city, or a graveyard. For step by step instructions have a look at our Places.

-

On the index page already entered entities are listed in a Table.

+

At the index page already entered entities are listed in a Table.

    -

  • Click on the + button to enter a new one.

    • -

  • Click on the name of an entry in the list to access the detail view.

    • -

  • To edit or delete an entry click on the Edit button in the detail view.

    • +

  • Click on the + button to enter a new one

    • +

  • Click on the name of an entry in the list to access the detail view

    • +

  • To edit or delete an entry, click on the Edit button in the detail +view.

Form fields

@@ -133,12 +134,12 @@

Form fieldsReference System

-

You can edit administrative units and historical places at Types in the +

You can edit administrative units and historical places under Types in the Places tab.

Administrative Unit

Hierarchy of administrative units in which the place is located, e.g. Austria, -Italy and their respective subunits like Lower Austria, Styria.

+Italy and their respective subunits like Lower Austria or Styria.

Historical Place

@@ -149,35 +150,37 @@

Historical Place

Can be linked via tabs to

    -

  • Source - when it is referenced there

    • -

  • Event - link new events. It’s not possible to link to existing events -from here, this has to be done from the events itself

    • +

  • Source - if a source refers to a place

    • +

  • Event - you can link a place to a newly created event. It’s not +possible to link to existing events in this way; you can link a place to +an existing event via the event’s form though

  • Reference

  • Artifact

    • -

  • Actor - only creation of new actors (using the place as a residence) -is supported here because for linking to existing actors there would be too -much possibilities

    • -

  • Feature - its subunit

    • +

  • Actor - you can link a place to a newly created actor. It’s not +possible to link to existing actors in this way; you can link a place to +an existing actor via the actor’s form though

    • +

  • Feature - as subunit of a place (for more information see below)

  • File

Places and their subunits

-

In OpenAtlas a place is a physical thing that has a certain position and/or -extends in space that can be connected to various other information (temporal, -spatial, events, sources etc.). Furthermore, places can be divided into -multiple subunits to record archaeological information. For more information -on those subunits see Feature, Stratigraphic unit, -Artifact, and Human remains as well as a detailed workflow example -(Archaeological data).

-

An example of a place would be a graveyard. That place is the superior unit. +

In OpenAtlas a place is a “physical thing” (CIDOC CRM +E18Physical Thing) that has a certain +position and/or extends in space. It can be connected to various +other information (temporal, spatial, events, sources, etc.). Furthermore, +places can be divided into multiple subunits to record archaeological +information. For more information on subunits see Feature, +Stratigraphic unit, Artifact, and Human remains +as well as a detailed workflow example (Archaeological data).

+

An example of a place would be a graveyard. The place is the superior unit. Each grave of this cemetery is considered a Feature that forms the cemetery. Each of those graves is composed of one or many subunits -(Stratigraphic unit). This would be the burials in the very grave -(e.g. a primary and a secondary burial) and the back filling. Each -stratigraphic unit may have associated Artifact belonging to the -respective unit: e.g. the grave goods of one of the burials, the artifacts -found in the back filling. Anthropological information can be added via +(Stratigraphic unit)such as burials in the very grave +(e.g. a primary and a secondary burial) and its back filling. Each +stratigraphic unit may have associated Artifact, e.g. the grave goods +of one of the burials or artifacts found in the back filling. +Anthropological information can be added via Human remains - another subunit of stratigraphic unit.

../_images/sub_unit.jpg
diff --git a/openatlas/static/manual/entity/reference.html b/openatlas/static/manual/entity/reference.html index 87451ae76..1fdb21bc3 100644 --- a/openatlas/static/manual/entity/reference.html +++ b/openatlas/static/manual/entity/reference.html @@ -111,15 +111,16 @@

ReferenceE31 Document

    -

  • Bibliography - e.g. book, inbook or article

    • +

  • Bibliography - add book, inbook, or article

  • Edition - e.g. charter editions or chronicle edition

    • -

  • External Reference - e.g. URLs of websites or DOIs

    • +

  • External Reference - such as URLs of websites or DOIs

-

On the index page already entered entities are listed in a Table.

+

At the index page already entered entities are listed in a Table.

    -

  • Click on the + button to enter a new one.

    • -

  • Click on the name of an entry in the list to access the detail view.

    • -

  • To edit or delete an entry click on the Edit button in the detail view.

    • +

  • Click on the + button to enter a new one

    • +

  • Click on the name of an entry in the list to access the detail view

    • +

  • To edit or delete an entry, click on the Edit button in the detail +view.

Form fields

@@ -131,8 +132,9 @@

Form fields

Citation example

-

At Content an example citation can be defined which will be displayed under the -form at insert/update of an edition or a bibliography.

+

Via Content an example citation can be defined which will be +displayed under the form during the insert/update of an edition or a +bibliography.

Can be linked via tabs to

@@ -143,9 +145,10 @@

Can be linked via tabs toPlace

  • File

    • -

    When linking a Bibliography or Edition a page can be defined.

    -

    When linking an External Reference a link text can be specified which be shown on the -info page of referenced entities. In case no link text was provided the URL will be shown instead.

    +

    While linking a Bibliography or Edition a page can be defined.

    +

    While linking an External Reference a link text can be specified which +be shown on the info page of referenced entities. In case no link text is +provided the URL will be shown instead.

    diff --git a/openatlas/static/manual/entity/reference_system.html b/openatlas/static/manual/entity/reference_system.html index 9647c47a2..8c50cdfa8 100644 --- a/openatlas/static/manual/entity/reference_system.html +++ b/openatlas/static/manual/entity/reference_system.html @@ -111,28 +111,30 @@

    Reference SystemE32 Authority Document

    -

    Reference systems can be used to link entities to external sources. You can -see a list of available systems by clicking the Reference system button on -the start page.

    -

    Linking entities to external reference systems has many advantages like -being able to find or provide more information from other sources and it makes -it a lot easier to merge/compare data from other projects using the same -reference systems.

    -

    For step by step instructions to add a reference system have a look at our +

    Reference systems can be used to link entities to external sources. A list with +available reference systems is provided when clicking the +Reference system button on the start page.

    +

    Linking entities to external reference systems has many advantages such as +being able to find or provide more information from other sources. Futhermore, +they facilitate the merge of data sets. By using reference systems LOD (Linked +Open Data) can be created. +Furthermore, analogue reference systems such as library catalogues or +inventory numbers of a museum can be used in this way.

    +

    For step by step instructions how to add a reference system have a look at our References Systems example.

    Included by default

    -

    These systems are included in the default application. Furthermore, -it was made use of their APIs to provide search functionality inside of -OpenAtlas and display their information about already linked entities at the -corresponding entity detail view.

    +

    The following reference systems are pre-installed. By using their provided +APIs, OpenAtlas can provide search functionality in the respective form fields +and display information about already linked entities in the corresponding +entity detail view.

    Wikidata

    Wikidata is a collaboratively edited multilingual knowledge graph hosted by the Wikimedia Foundation. It is a common source of -open data that Wikimedia projects such as Wikipedia, and anyone else, is able -to use under the CC0 public domain license.

    -

    By default it is usable for places, persons and groups.

    +open data for Wikimedia projects such as Wikipedia. Everyone is able +to use the information under the CC0 public domain license.

    +

    By default it is usable for places, persons and groups within OpenAtlas.

    GeoNames

    @@ -140,18 +142,19 @@

    GeoNames

    GND

    The GND or Gemeinsame Normdatei (translated as Integrated Authority File) is an international authority -file for the organisation of personal names, subject headings and corporate +file for the organisation of personal names, subject headings, and corporate bodies from catalogues. It is used mainly for documentation in libraries and increasingly also by archives and museums.

    -

    By default it is usable for persons.

    +

    By default it is usable for persons in OpenAtlas.

    @@ -160,50 +163,53 @@

    Usage adding or updating an entity.

    ID

    -

    The identifier of the entity in the external reference system. For GeoNames -and Wikidata it will be checked for a valid format.

    +

    The identifier of an entity in the external reference system. For GeoNames +and Wikidata IDs will be checked for a valid format.

    Precision

    When linking to an external reference a precision is required. Available options are the SKOS based definitions -of the confidence degree that concepts can be used interchangeable.

    +of confidence degree.

      -

    • Close match: Concepts are sufficiently similar that they can be used -interchangeably in some information retrieval applications

      • -

    • Exact match: High degree of confidence that the concepts can be used +

    • Close match: Concepts (here a dataset in OpenAtlas and a dataset in an +external reference system) are sufficiently similar, therefore they can be +used interchangeably in some information retrieval applications

      • +

    • Exact match: High degree of confidence that the concepts (a dataset in +OpenAtlas and a dataset in an external reference system) can be used interchangeably

    -

    E.g. if a historical project links the city of Vienna to Wikidata, a -close match would be more suitable, because the Wikidata entry is more -about the current city and not the historical one.

    +

    E.g. if a historical project links the city of Vienna in Wikidata, a +close match would be more suitable, as the Wikidata entry deals +primarily with the current city Vienna and not the historical place.

    Configuration

    -

    Admins and manager can add, update and delete external reference systems.

    +

    Admins and manager can add, update, and delete external reference systems.

      -

    • Name - e.g. Wikipedia; can not be changed for Wikidata or GeoNames

      • -

    • Website URL - an URL to the project site of the reference system

      • -

    • Resolver URL - an URL that can be linked to in combination with an ID, -e.g. the resolver URL https://www.wikidata.org/wiki/ would create -together with a Q123 -identifier the external link: https://www.wikidata.org/wiki/Q123

      • -

    • Example ID - an example id to show the desired format e.g. Q123 -for Wikidata

      • +

    • Name - e.g. Wikipedia; the name can not be changed for the +pre-installed reference systems Wikidata and GeoNames

      • +

    • Website URL - URL of the reference system (e.g. +Wikidata for Wikidata)

      • +

    • Resolver URL - URL that - in combination with the ID - links to an +entity in the reference system (e.g. the resolver URL +https://www.wikidata.org/wiki/ in combination with the ID Q123 +creates the external link: https://www.wikidata.org/wiki/Q123 (September)

      • +

    • Example ID - an example id to show the desired format (e.g. Q123 +for Wikidata)

    • External reference match - default precision selected in forms

    • Description - a short description, shown in forms when mouse over the i icon

    • Classes - a checkbox list of available classes, for GeoNames only place is available

    -

    Classes can be removed from a system by clicking on the tab with the +

    Classes can be removed from a reference system by clicking on the tab with the corresponding class name and clicking the Remove button. This button is -only available if there are no entities of this class linked to the reference -system.

    +only available if there are no entities of this class linked to it yet.

    Reference systems can be deleted only if no classes are attached to it. -Wikidata and GeoNames are integrated and cannot be deleted but if desired they -can be disabled by removing the classes.

    +Wikidata and GeoNames are integrated into OpenAtlas and cannot be deleted but, +if desired, can be disabled by removing the classes.