Redmine: Issueshttps://redmine.openatlas.eu/https://redmine.openatlas.eu/favicon.ico?17112826112024-02-22T14:51:33ZRedmine
Redmine 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 - Feature #2171 (Acknowledged): Autocomplete form fieldshttps://redmine.openatlas.eu/issues/21712024-02-01T12:09:16ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<p>Like discussed in the last developer <a class="wiki-page" href="https://redmine.openatlas.eu/projects/uni/wiki/Meeting_2024-01-31">meeting</a> to counter possible performance issues for projects with big data sets we will try out the approach using autocomplete fields.<br />Advantage would be that data is only loaded when typing into respective fields instead loading data tables for all fields every time.</p>
<p>Because this is experimental we will keep it optional and configurable in the profile to use this approach.<br />One good suggestion from Stefan (Probst) was to not limit the results but make them "endless" scroll-able. We could try this out with already existing GeoNames and Wikidata fields.</p> OpenAtlas - Feature #2152 (Acknowledged): Annotations: check orphan functionhttps://redmine.openatlas.eu/issues/21522024-01-12T15:59:28ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
Currently it is only possible to link entities to an annotation if the entity is already linked to the file. This is the intended behavior to prevent linking entities just via annotation and outside the model.<br />But it might than happen, that the model link (refer to) is removed and we thought about how to deal with this situation:
<ul>
<li>Automatically remove the annotation would be to destructive</li>
<li>Preventing or warning to remove the (refer to) link would be cumbersome e.g. there could be multiple and so we would have to check if it is the last one and so on. Also it might not happen often, if at all.</li>
</ul>
At the moment our approach would be to add a data check function to list entities that have a connection to file a via an annotation but are not linked via the model (referred to). This approach would have some advantages:
<ul>
<li>No destructive behavior</li>
<li>After listing all "orphaned" annotation links, it could be offered to
<ul>
<li>Delete the annotation</li>
<li>Remove the entity from the annotation</li>
<li>Re-link the entity used in the annotation to the file again</li>
</ul></li>
</ul> OpenAtlas - Feature #2133 (Acknowledged): Better file statshttps://redmine.openatlas.eu/issues/21332023-11-27T13:09:00ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<p>While adapting and testing Kubernetes installations we noticed that our free disk function is too general with only looking at the /files directory as a whole.<br />In this case some sub directories are mounted on different shares which broke our free disk calculation.<br />Also while at it, we should look into IIIF file usage a well.</p> OpenAtlas - Feature #2129 (Acknowledged): Attributions for fileshttps://redmine.openatlas.eu/issues/21292023-11-24T11:17:35ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<p>Like discussed in yesterdays developer meeting we will add a more standard way to add information about file attribution.<br />We will take care of other related issues first but feel free to already add ideas about it here.</p>
<strong>Ideas</strong>
<ul>
<li>Creator</li>
<li>License holder</li>
</ul> OpenAtlas - Feature #2093 (Acknowledged): API v1: Using marshmallow for object serializationhttps://redmine.openatlas.eu/issues/20932023-10-20T10:56:29ZBernhard Koschiček-Krombholz
<p><a href="https://flask-restful.readthedocs.io/en/0.3.8/reqparse.html" class="external">Flask-RESTful</a> suggests using <a href="https://marshmallow.readthedocs.io/en/stable/" class="external">marshmallow</a> to serialize data instead of their own package. This will be necessary to handle more complex parameters.</p> OpenAtlas Discovery - Feature #2044 (Acknowledged): Additional language featureshttps://redmine.openatlas.eu/issues/20442023-08-09T08:38:30ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<p>At the moment only English and German languages are supported for the user interface and the (user managed) content.<br />To make it more generic it should be possible to add additional content languages even if no user interface translations are available.<br />Maybe in combination with being able to set an extra user interface language too.</p>
<p>This feature has no high priority at the moment. Please indicate here in case you want them implemented.</p> OpenAtlas - Feature #1992 (Acknowledged): Advanced website featureshttps://redmine.openatlas.eu/issues/19922023-03-22T15:10:49ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<p>A collection of ideas form the workshop today to further improve our project website: <a class="external" href="https://openatlas.eu">https://openatlas.eu</a></p>
<ul>
<li>Better navigation for news and event items, e.g. make years fold-able or provide links at the top</li>
<li>Tags for projects, e.g. similar to <a class="external" href="https://craws.net">https://craws.net</a></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 - Feature #1962 (Acknowledged): API: Entity export functions as Markdownhttps://redmine.openatlas.eu/issues/19622023-02-09T17:02:15ZEnric Rodellas
<p>See file sections for format suggestion.</p>
<hr />
<p>Add a button in each item/form of Source, Event, Actor, Place, Artifact, Reference, Types that allows to export to print, PDF, Word, markdown, JSON, etc, and also the possibility to apply recursively to a selected group of items<br />I think it would be very useful get a kind of printed record of a items, containing all items related. <br />for example, when I export an Actor I would like to get sources, events, relations, members of, Artifacts, references, Files, Notes related to this actor.</p>
<p>I you Alex do a kind of seed/example, I would try to complete and format others, with my low level of Python, but effective.</p> OpenAtlas - Feature #1749 (Acknowledged): API: Testsystems for API https://redmine.openatlas.eu/issues/17492022-06-14T14:43:05ZBernhard Koschiček-Krombholz
<p>It would be a good idea, to automatically test our API output. We will start with looking at: <a class="external" href="https://github.com/p1c2u/openapi-core">https://github.com/p1c2u/openapi-core</a></p> OpenAtlas - Feature #1573 (Acknowledged): 3d geometrieshttps://redmine.openatlas.eu/issues/15732021-09-11T14:28:21ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<p>In the INDIGO projects we will receive additional 3d geometry data. So far we only map points, lines and polygons so we need another geometry type (with height).<br />We will also use this opportunity to merge all GIS data into one table and move into the model schema (instead using a dedicated GIS schema)</p>
<p>In the first version they will be shown on the map but without functionality to add or edit them manually.</p>
<strong>To consider</strong>
<ul>
<li>Adapting database (see merge suggestion above)</li>
<li>How do we import them (INDIGO workflow specific)</li>
<li>How do we present them on the map, I guess it should be possible to "flatten" them</li>
<li>How to prevent them being overridden when working with maps the "classic" way</li>
</ul> OpenAtlas - Feature #1553 (Acknowledged): Boolean search operatorshttps://redmine.openatlas.eu/issues/15532021-07-29T10:26:39ZBecca Grose
<p>Might it be possible to enable Boolean search functionality on the OpenAtlas user interface?</p>
<pre><code>Currently, it does not seem to work (at least on the CONNEC database) and I'm not sure if this is design or a bug. If it were easy to introduce, it would be very useful for us and even more useful for end users.</code></pre>
<p>Absolutely understand if this isn't possible!</p> OpenAtlas - Feature #1499 (Acknowledged): Adding references to imageshttps://redmine.openatlas.eu/issues/14992021-04-15T12:26:35ZNina Richards
<p>As for <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Adding references to subunits (citation) (Closed)" href="https://redmine.openatlas.eu/issues/1216">#1216</a> it would be handy to get a list of references already used in connected subunits but also the place for images.</p> OpenAtlas - Feature #1233 (Acknowledged): API: External Authentication https://redmine.openatlas.eu/issues/12332020-05-10T08:34:26ZBernhard Koschiček-Krombholz
<p>External Authentication will be needed for projects who want a frontend without exposing all data (no public API).<br />For implementing an API authentication method see: <a class="wiki-page" href="https://redmine.openatlas.eu/projects/uni/wiki/API_Authentication">Whitepaper</a>, <a href="https://realpython.com/token-based-authentication-with-flask/" class="external">authentication-with-flask</a></p>
<p>To consider: webclients will request data so we can't e.g. just block IPs or similar.</p>