Redmine: Issueshttps://redmine.openatlas.eu/https://redmine.openatlas.eu/favicon.ico?17112826112024-03-22T10:58:51ZRedmine
Redmine 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 - 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 - 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 #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 #2128 (Acknowledged): Option to mark files for public viewinghttps://redmine.openatlas.eu/issues/21282023-11-24T11:14:50ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<p>We will implement an option if files can be made available for the public (at a later point) configurable per file as discussed in yesterdays developer meeting.<br />This information can than be used at e.g. presentation sites.</p>
Some ideas:
<ul>
<li>Default will be to allow public viewing but can be configured to not allow it</li>
<li>Provide "strong" display hints in the backend when looking at a file</li>
<li>Add this information to the file list</li>
</ul> 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 #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 - Feature #2079 (Acknowledged): Text annotationhttps://redmine.openatlas.eu/issues/20792023-09-25T14:17:47ZAlexander Watzingeralexander.watzinger@oeaw.ac.at
<p>Text annotation has been on our radar for some time now so I created an issues to discuss how we can proceed.<br />Basically it's about linking entities (actors, places, ...) to specific parts of a text, instead of just linking them to the whole text like it is possible currently.</p>
<p>White paper: <a class="wiki-page" href="https://redmine.openatlas.eu/projects/uni/wiki/Text_annotation">Text annotation</a></p> OpenAtlas - Feature #2035 (Acknowledged): Linked Open Data https://redmine.openatlas.eu/issues/20352023-07-04T14:17:00ZBernhard Koschiček-Krombholz
<p>OpenAtlas has an API, where data can be exported in different formats (RDF/XML, Turtle, n3, etc.) except from JSON. These formats are automatically created from the Linked Places Format (JSON) and are not tested against completeness and the <a href="https://5stardata.info/" class="external">5-star deployment scheme</a>. <br />Since the FAIR principles are very important for OpenAtlas, we should work on an appropriate interface for exporting the data as RDF in the sense of the Linked Open Data paradigm.</p>
<strong>To do:</strong>
<ul>
<li>Talk with specialists at the ACDH-CH</li>
<li>Look into SPARQL</li>
<li>RDF export
<ul>
<li>From Linked Open Arts</li>
<li>Create them manually</li>
</ul>
</li>
<li>How to test if it fits semantic web</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 #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>