Redmine: Issueshttps://redmine.openatlas.eu/https://redmine.openatlas.eu/favicon.ico?17112826112024-03-26T17:31:55ZRedmine
Redmine OpenAtlas - Feature #2244 (Assigned): Import of place hierarchyhttps://redmine.openatlas.eu/issues/22442024-03-26T17:31:55ZBernhard Koschiček-Krombholz
<p>This is a follow-up ticket from <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Enhanced Import (Closed)" href="https://redmine.openatlas.eu/issues/1567">#1567</a> Enhanced Import.<br />Since all prerequisites are met, the import of a place hierarchy can be implemented. <br />As example structure, Stefan Eichert provided this CSV: <a class="external" href="https://docs.google.com/spreadsheets/d/1IIPGKvSRNi6Qeir6070VS4u7uvHdlpYenEhRkCaGJcI/edit?usp=sharing">https://docs.google.com/spreadsheets/d/1IIPGKvSRNi6Qeir6070VS4u7uvHdlpYenEhRkCaGJcI/edit?usp=sharing</a></p>
To-do:
<ul>
<li>Add new import button "Place hierarchy" </li>
<li>Link existing references with ID including page number</li>
<li>OpenAtlas Class name to know which level the place is</li>
<li>Parent import ID</li>
</ul> OpenAtlas - Question #2240 (In Progress): Questions about the user interfacehttps://redmine.openatlas.eu/issues/22402024-03-22T11:10:28ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<p>Questions from Lara:</p>
<ul>
<li>Can the order of form elements be changed?</li>
<li>Are free text fields possible?</li>
<li>Are general layout changes at forms possible?</li>
</ul>
<p><img src="https://redmine.openatlas.eu/attachments/download/1016/questions.png" alt="" loading="lazy" /></p> OpenAtlas - Administration #2239 (In Progress): Server movehttps://redmine.openatlas.eu/issues/22392024-03-22T10:58:51ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<p>Because our (private) server is acting up we will move to a new server.<br />This only affects "general" sites like the OpenAtlas project site, demo versions, Redmine, ... and not OpenAtlas instances for cooperations which are hosted on different servers (mostly at the ACDH-CH).</p> OpenAtlas Discovery - Bug #2238 (Assigned): Proper git tag/release version not show in footerhttps://redmine.openatlas.eu/issues/22382024-03-19T10:39:37ZMoritz GroßfurtnerOpenAtlas - Feature #2223 (In Progress): Refactor and minor improvementshttps://redmine.openatlas.eu/issues/22232024-02-28T11:25:59ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<strong>To do</strong>
<ul>
<li>Forms: move entity collection from table form fields to form manager</li>
</ul> OpenAtlas Discovery - Bug #2215 (In Progress): Details View: Too many images break the viewhttps://redmine.openatlas.eu/issues/22152024-02-27T17:12:50ZMoritz Großfurtner
<p>For entities that have a lot of images connected to them, the image viewer breaks. <br />At the moment about 10 images is the maximum. It might have something to do with the "Carousel" component.</p>
<p>Examples can be found by navigating to a license type as those often have a lot of images associated with them, but a concrete example would be entity <a href="https://openatlas-discovery-demo.acdh-ch-dev.oeaw.ac.at/en/entities/20158" class="external">20158</a><br />on the demo dev site using data from the Thanados project.</p> OpenAtlas - Feature #2200 (Assigned): API: Expand LPF formathttps://redmine.openatlas.eu/issues/22002024-02-22T14:51:33ZBernhard Koschiček-Krombholz
<p>For OpenAtlas Discovery we decided to make a new format out of Linked Places so we can experiment and test it without breaking the original format. In the end of this process, this format will most likely replace the current LPF. All changes are always in the current develop branch and I will not keep track, which change made it to the current main branch. <br />Please feel free to add to-dos.</p>
<p><strong>To do</strong>:</p>
<strong>Done</strong>:
<ul>
<li>Added <code>relations.relationTypeLabel</code> to have the property label without property code and the right <code>locale</code> (<code>?locale=[en, de, ca, es, fr]</code>) if available.</li>
<li>Changed <code>relations.relationType</code> to the correct reference with <code>_</code>, eg. <code>crm:P2_has_type</code></li>
</ul> OpenAtlas Discovery - Feature #2164 (Assigned): CMS: Inform users about deplay delay via success ...https://redmine.openatlas.eu/issues/21642024-01-23T10:24:58ZMoritz GroßfurtnerOpenAtlas Discovery - Feature #2163 (In Progress): Documentation for Decaphttps://redmine.openatlas.eu/issues/21632024-01-22T14:04:30ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
It would be nice to have a documentation/help button at the main menu on top.<br />For now a very basic documentation would suffice, we can extend it than as needed. Some important points for now would be:
<ul>
<li>General instruction how to navigate</li>
<li>Explain that deployment will always need some time to see it live</li>
<li>Make aware that content (text and images) is public visible in GitHub (even if they just try something out)</li>
</ul> OpenAtlas - Feature #2127 (In Progress): Linking artifacts with other artifactshttps://redmine.openatlas.eu/issues/21272023-11-23T17:19:53ZNicholas Melvani
<p>I would like to show that a manuscript (B) was copied from another manuscript (A). I can obviously use the production event, but I would like to be able to show the relationship, i.e., that manuscript B is a copy of manuscript A (and vice versa).</p> OpenAtlas - Feature #2105 (In Progress): New file license systemhttps://redmine.openatlas.eu/issues/21052023-11-03T12:34:22ZBernhard Koschiček-Krombholz
<p>Because of the increasing requirements (e.g. URL for licenses in IIIF) we decided to implement a new license system for files.</p>
<strong>Implementation</strong>
<ul>
<li>New license system (de-coupled from types)</li>
<li>Configurable at <code>admin/files</code></li>
<li>Option to add an URL and/or text</li>
</ul> OpenAtlas - Feature #2011 (Assigned): Replace network vizualisationhttps://redmine.openatlas.eu/issues/20112023-04-29T12:13:49ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<p>When implementing <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Egocentric network display for entities (Closed)" href="https://redmine.openatlas.eu/issues/2005">#2005</a> I noticed some issues with our network visualizations. E.g. the 2D and 3D views have missing labels for the outermost nodes</p>
Some notes about implementation:
<ul>
<li>Either update d3 libraries or switch to different libraries to get rid of vulnerability warnings in current version</li>
<li>We want to use it for the OpenAtlas Discovery too, so developing it as reusable component or similar would be beneficial</li>
</ul>
<ul>
<li>Features
<ul>
<li>We can drop the 2D and 3D views for now</li>
<li>Nodes should be clickable providing a popup with additional information and a link to the entity default view (similar to the map view)</li>
<li>Color and dimension management, ability to print, ... like before so that people can create a nice image of their project data network</li>
<li>Maybe we implement selection of classes and/or properties but we would have to look at that in detail</li>
</ul></li>
</ul> OpenAtlas - Feature #1980 (In Progress): API: Improve LOUDhttps://redmine.openatlas.eu/issues/19802023-03-03T11:59:00ZBernhard Koschiček-Krombholz
<p>This issue is for further improvements of the LOUD format.</p>
<p><strong>Question/answer/implementation</strong></p>
<p>Q: Which property have the comments of the timespans? My guess is <a href="https://cidoc-crm.org/Property/p3-has-note/version-7.1.1" class="external">P3 has note</a><br />A:<br />I:</p>
<p><del>Q: Would it be possible to have the main image implemented in the JSON-LD in the following way (based on <a class="external" href="https://linked.art/example/person/13.json">https://linked.art/example/person/13.json</a>)<br />A: Yes, it should be possible to display the main image. <br />I: The main image of an entity is shown with the "representation" key. But only image, which are actively marked as main image.</del></p>
<p>N: Include the shortcuts provided by <a class="external" href="https://manual.openatlas.eu/model/openatlas_shortcuts.html">https://manual.openatlas.eu/model/openatlas_shortcuts.html</a><br />I:</p> OpenAtlas Discovery - Feature #1892 (In Progress): Network visualizationhttps://redmine.openatlas.eu/issues/18922022-11-24T17:21:38ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<p>A network visualization similar too: <a class="external" href="https://demo.openatlas.eu/overview/network/">https://demo.openatlas.eu/overview/network/</a><br />Also, smaller individual entity centered ego networks would be a cool idea. I'm thinking about that for the backend too.</p> OpenAtlas - Feature #1525 (Acknowledged): Model: Spacetime Volume E92https://redmine.openatlas.eu/issues/15252021-06-02T11:11:16ZVincent Ducatteeuwvincent.ducatteeuw@ugent.be
<p><strong>Context:</strong><br />In OpenAtlas “Place’ is used as a label for a combination of multiple CRM entities. It is the “E18 Physical Thing” - that represents for example a settlement, a church or a castle - combined with an “E53 Place” entity that represents its space/location. The location is combined with a “E94 Space Primitive” and stored as a PostGIS geometry.</p>
<p><strong>Issue:</strong> <br />Currently multiple geometries and toponyms can be assigned to a “Place”. However, temporally dating these geometries and toponyms is not possible. For example, it is not possible to say that New York was named “Nieuw Amsterdam” during the 17th century and "New York" during the 18th century. (This is possible in the ongoing GeoJSON-T format).</p>
<p><strong>Proposal:</strong><br />If possible, I would suggest adapting the current OpenAtlas/CIDOC CRM data model to incorporate temporally dating geometries and toponyms through the use of the “E92 Spacetime Volume” and its properties “P160_has_temporal_projection” and “P161_has_spatial_projection” (Schneider et al., 2019)</p>
<p>“E18 Physical Thing” is a subclass of E92 and inherits these properties. If my understanding is correct, a time-span can be assigned to an “E18 Physical Thing” during which a toponym and geometry is valid. Multiple E18s with a timespan can refer to the same place. For example, an E18 entity referring to a city during the 17th century and an E18 entity referring to the same city in the 18th century. These timed observations can be linked to a new E18 that refers to the city from it’s beginning to its end via the property “P10_falls_within”. As attachment, I have provided an UML representation of the CIDOC CRM Classes. If my reasoning is incorrect, I will try to adapt the model as soon as possible.</p>
<p>This addition to the model would be very beneficial for the development of historical gazetteers and the mapping to GeoJSON-T.</p>