Agenda
- 10:00 - 10:10 Introduction
- 10:10 - 10:15 State and capacities of development
- 10:10 - 10:30 Exchange of experiences with re³gistry
- 10:30 - 10:45 Current needs for operation
- 10:45 - 10:50 Break
- 10:50 - 11:15 Issue discussion and prioritization
- 11:15 - 11:30 Reserved for technical hands-on
Participants
BKG, CNIG (ES), BE Vallonian District, Bilbomatica
Project state
Issues
Migration Assistant
#1 Migrating custom attributes fails
DescriptionMigration assistant fails if database contains custom attributes |
#2 Migrating multiple languages fails
| reported by | NLS-FI |
|---|
| Github Ticket |
|
|---|
|
|
|---|
|
|
|---|
|
|
|---|
DescriptionWhen multiple languages where present in 1.3, only English is presented in 2.x after migration. |
#8 Encoding problems
| reported by | CNIG (Spain) |
|---|
| Github Ticket |
|
|---|
|
|
|---|
|
|
|---|
|
|
|---|
DescriptionComment |
URL Handling
#5 web.application_root_url is oftentimes neglected +
DescriptionURLs that are presented on forwards and as links in returned documents oftentimes do not follow the configuration parameter web.application_root_url. Sometimes they contain the local adress of the backend webserver, sometimes even different values from the re³gistry database (eg. https://github.com/ec-jrc/re3gistry/issues/438#issuecomment-2186367203). CommentsThis needs to be resolved, as it hinders using the software and is a security threat. |
#9 Link for item validation redirection 404 +
General Problems/Bugs
#11 Library Update Needed
Description- Libraries where not updated and software depends on old legacy versions of Java, Tomcat, Postgresql etc.
- Dependencies need to be thoroughly checked, at least compatibility with tomcat 10 is needed.
Comment |
#3 REST Service does not omit log +
#4 REST Service does not return data +
Description- No changes to rights on a register possible
Comment |
#6 Owner, Controlbody and other Groups of Register cannot be changed
Description- No changes to rights on a register possible
Comment |
#10 Bulk import hierarchical items fails
| reported by | Servizio Gestione dati e banche dati (IT) |
|---|
| Github Ticket | |
|---|
|
|
|---|
|
|
|---|
|
|
|---|
Description- Each subclass needs to be uploaded seperately → process becomes too lengthy
Comment |
#7 Development Container Environment needed
| reported by | BKG |
|---|
| Github Ticket |
|
|---|
|
|
|---|
|
|
|---|
|
|
|---|
DescriptionComment |
#3 Email templating problems
Documentation
#3 First documentation overhaul
| reported by | BKG, NLS-FI |
|---|
| Github Ticket |
|
|---|
|
|
|---|
|
|
|---|
|
|
|---|
Description- Documentation doesn’t match with actual procedures, especially in installation and data migration
- Front-end not documented
Comment |
Template
#3 Template
| reported by | BKG |
|---|
| Github Ticket |
|
|---|
|
|
|---|
|
|
|---|
|
|
|---|
DescriptionComment |
Prioritization
Minutes:
The migration from 1.5 to 2.3 did not work. The Issue was reportet and confirmed. But for the time beeing there were no ressources to solve it.
Migration from 1.3 to 2.x did not work either.
The Templates from 1.3 and 1.5 are very different.
2.0-2.5 did not work The error was a 404.
The backend cannopt be installed. This issue was reported.
Spain has not yet shared the many work-arounds they have tried sofar.
As the issues are identified, there must be something done for them to work.
High on the priority list is to update the software to get the migration to workor but the ressourses are limited and the issue cannot be adressed at the moment.
https://github.com/ec-jrc/re3gistry/issues/427#event-13612044672
https://github.com/ec-jrc/re3gistry/issues/476
The issues stated by spain seem to be similar to the German ones.
Wallon Region Belgium is on Version 1.3. They have not tried to update because they new of the many problems beforehand. So the update was not executed. In Belgium the Registry was not used much. The Idea was to use it more in the future. There is no testing environment to test the 2.x versions.
Jane Heller (DE) says it would be good to teest the different versions in different places. This way we can see if there are the same problems everywhere.
Since the software will be updated in summer it must work then - or at least something must be working by thenn.
from the 1.x versions to the 2.x versions.
Spains first approach was to migrate. The second was to deploy and populate manually.
We Germany will try to talk to Jordi about priorization.
Next Steps
Issues