Activity
From 2024-02-29 to 2024-03-29
2024-03-29
- 16:41 Question #2240 (Closed): Questions about the user interface
- Closing this questions after it was also discussed at our last [[Meeting_2024-03-27|meeting]].
- 16:04 Feature #2244 (In Progress): Import of place hierarchy
- 16:00 Feature #2246 (Acknowledged): Sorting of related entities in views and forms
- 16:00 Feature #2246 (Closed): Sorting of related entities in views and forms
- As Lara pointed out in our last meeting [[Meeting_2024-03-27|meeting]] the order at multi type select fields is diffe...
2024-03-28
- 17:37 Feature #2245: API: Adding import functions for TIB Terminology Service
- If it is possible to publish that easily in a Skosmos service, yes you can do that.
- 15:09 Feature #2245: API: Adding import functions for TIB Terminology Service
- For the moment, can I export the RDF file from the TIB terminology service, then publish it as a Skomos server like h...
- 14:33 Feature #2245 (Acknowledged): API: Adding import functions for TIB Terminology Service
- To answer this in general: currently OpenAtlas provides functionality to import vocabularies from "Vocabs":https://vo...
- 13:40 Feature #2245 (Acknowledged): API: Adding import functions for TIB Terminology Service
I was wondering if the current version would allow me to import the vocabulary collections from a terminology servi...- 12:04 Feature #2158: Georeferencing files for multiple places (overlay)
- Yes, I missed that we can drop the *link_id* too (I edited my former comment accordingly) but would argue to leave th...
- 11:52 Feature #2158: Georeferencing files for multiple places (overlay)
- Sorry, I didn't mean in the image, because reading GeoTIFFs would be another big feature. Yesterday I had no further ...
- 11:51 Feature #2158: Georeferencing files for multiple places (overlay)
- Overlay data is stored in database table *web.map_overlay* with values:
* image_id
* place_id
* link_id
* boundin... - 09:04 Feature #2158: Georeferencing files for multiple places (overlay)
- Yes, the possibility to use GeoTIFFs (https://www.ogc.org/standard/geotiff/) might be a partial solution. However, fr...
2024-03-27
- 16:29 Feature #2158: Georeferencing files for multiple places (overlay)
- Since a georeferenced image should always use the same coordinates, maybe it is better to store somehow the coordinat...
2024-03-26
- 18:57 Feature #1567 (Closed): Enhanced Import
- Closing this issue and move place hierarchy related tasks to #2244.
- 18:31 Feature #2244 (Closed): Import of place hierarchy
- This is a follow-up ticket from #1567 Enhanced Import.
Since all prerequisites are met, the import of a place hierar... - 13:04 Feature #2241 (Closed): Manual: Subordinate artifacts (and places)
- I added information about sub artifacts to the manual and it will be part of the next release.
Thank you again for r...
2024-03-25
- 17:17 Feature #2243 (Acknowledged): Persistent identifiers for transformed actors/artifacts etc.
- This sounds like an interesting idea and thank you for giving such a detailed and useful example to illustrate this.
... - 14:13 Feature #2243 (Acknowledged): Persistent identifiers for transformed actors/artifacts etc.
- It would be very useful to be able to have persistent identifiers for things which have been transformed, so that sea...
- 17:04 Feature #2242 (Acknowledged): Contextual/hierarchical arrangement of subordinate items
- Thank you for this suggestion. Like discussed we already like the idea because it would make the data much more acces...
- 13:50 Feature #2242 (Acknowledged): Contextual/hierarchical arrangement of subordinate items
- Where various types under *E5 “events”* have subordinate events, it would be very useful to be able to toggle the vi...
- 14:20 Feature #2241: Manual: Subordinate artifacts (and places)
- *Artifacts*
It is possible that an artifact can be a "sub" artifact of another one. E.g. a sword can consist of a bl... - 14:09 Feature #2241 (In Progress): Manual: Subordinate artifacts (and places)
- 13:47 Feature #2241 (Closed): Manual: Subordinate artifacts (and places)
- *Update*
Because of the questions below it came apparent that some parts about adding sub artifacts were missing in ...
2024-03-22
- 16:24 Feature #1567: Enhanced Import
- Alex pointed out, at the [[Meeting_2024-03-21|developer meeting]], that the implementation of external reference syst...
- 12:26 Feature #1567: Enhanced Import
- Added administrative unit and historical place:
|_.administrative_unit|_.historical_place|
| 87 | 102 |
- 12:28 Question #2240 (In Progress): Questions about the user interface
- Thank you for reporting.
*Can the order of form elements be changed?*
The order of displayed form fields is "fixe... - 12:10 Question #2240 (Closed): Questions about the user interface
- Questions from Lara:
* Can the order of form elements be changed?
* Are free text fields possible?
* Are general... - 11:58 Administration #2239 (Closed): Server move
- Because our (private) server is acting up we will move to a new server.
This only affects "general" sites like the O... - 09:26 Feature #2127 (In Progress): Linking artifacts with other artifacts
- As discussed in our OpenAtlas developer meeting, Bernhard may have found a model solution as noted by him here and wi...
2024-03-21
- 16:24 Feature #2127: Linking artifacts with other artifacts
- Can this be a possibility without shortcut: "E22(Human-Made Object)":https://www.cidoc-crm.org/Entity/e22-human-made-...
- 12:21 Feature #1567: Enhanced Import
- Included import of value types:
|_.value_type_ids|
| 666;12.34 777;987|
Again delimiter is @;@ for type_id;valu...
2024-03-19
- 08:24 Feature #1567: Enhanced Import
- Added external reference system with @id;identifier;match@
Not sure if ; is the optimal delimiter, but it is a start...
2024-03-14
- 17:25 Feature #1567: Enhanced Import
- Took some time, but I replaced northing/easting with WKT and therefore also support for Polygons and Linestrings.
2024-03-13
- 15:30 Feature #2230 (Acknowledged): Linking sources with other sources
- I have a drawing (SOURCE) containing the text of an inscription (SOURCE) written on a marble base (ARTIFACT). I have ...
- 12:32 Feature #2228 (Closed): API: Swagger UI adaptation
- If /swagger is called, it will create a new @openapi.json@ file in the folder @files/@ (so it won't be tracked by git...
2024-03-12
- 19:10 Feature #2228 (Closed): API: Swagger UI adaptation
- Since it led to confusion, that the server selection show always the demo version first, a adaptation of the OpenApi ...
2024-03-08
- 08:23 Feature #2106: IIIF: Delete IIIF images
- Thanks for implementing.
Because you have done quite some work recently, I uploaded recent additions to demo-dev (ht... - 08:00 Feature #2146 (Closed): IIIF: Display hints for possible problems
- In case we encounter other problems we might be able to catch before we will create a new issue.
Closing and assigni...
2024-03-07
- 16:52 Feature #1567: Enhanced Import
- By comparing the example and the current import, following things needs to be added:
* Alias*
* Geometry as WKT ... - 14:48 Feature #2193 (Closed): Import artifacts
- Included artifact to import. Is in develop branch.
- 13:15 Feature #2106 (Closed): IIIF: Delete IIIF images
- I added the delete all button to the IIIF settings and the delete single IIIF file under the profile image. We can di...
2024-03-06
- 18:31 Feature #2106: IIIF: Delete IIIF images
- Alexander Watzinger wrote in #note-2:
> I'm not sure why we need this. At one point we will implement that if IIIF i... - 18:24 Feature #2146 (In Progress): IIIF: Display hints for possible problems
- I added the check on submit, if there is a trailing slash. And if it is a valid URL.
If the IIIF path does not ex... - 15:25 Feature #2126 (Closed): IIIF: Polygons for annotation selection
- Added polygon as new possible geometry for image annotation. If other geometries are needed, feel free to make a new ...
2024-03-05
- 17:13 Feature #2126 (Assigned): IIIF: Polygons for annotation selection
- 17:12 Question #2225 (Closed): update from 8.1 to 8.2
- You're welcome.
- 17:11 Question #2225: update from 8.1 to 8.2
- Thank you so much. It works.
- 16:55 Question #2225: update from 8.1 to 8.2
- The problem is, that git thinks that you changed all these files manually. This can be caused by several things.
... - 16:41 Question #2225: update from 8.1 to 8.2
- it says:
On branch main
Your branch is behind /origin/main' by 237 commits, and can be fast-forwarde. (use "git pu... - 14:11 Question #2225: update from 8.1 to 8.2
- Git can be a little complicated.
Are you sure that you are on the main branch and not on develop?
What does @git s... - 15:35 Feature #2223 (In Progress): Improved forms
2024-03-04
- 21:11 Question #2225: update from 8.1 to 8.2
I ran the code to pull the origin but got the following message and the installation process was aborting
"Your ...- 09:09 Question #2225 (Assigned): update from 8.1 to 8.2
- For this update, no database update is needed. So you can skip @python3 install/upgrade/database_upgrade.py@
Prefe... - 08:22 Question #2225 (Closed): update from 8.1 to 8.2
It is my first update of the software so I want to make sure I am doing things correctly.
Should I first navigat...- 16:44 Question #2183 (Closed): Reference System and Vocabs Import
- In conclusion, it can be imported from VOCABS, but not updated. I will close this ticket, if new question arise feel ...
- 12:37 Bug #2184 (Closed): Directory for processed files not writable
- This is fixed in 8.2.1.
Thank you for reporting.
If you created the folder manually, you don't need to do anyth...
2024-02-29
- 12:50 Feature #1974: Reference management system for biblio references
- Found these libraries, which is also supported by bookworm:
* "bibtexparser":https://github.com/sciunto-org/pytho...
Also available in: Atom