Participants

Project state

Issues

Migration Assistant

#1 Migrating custom attributes fails

Description

Migration assistant fails if database contains custom attributes

#2 Migrating multiple languages fails

Description

When multiple languages where present in 1.3, only English is presented in 2.x after migration.

URL Handling

#5 web.application_root_url is oftentimes neglected

Description

URLs 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).

Comments

This needs to be resolved, as it hinders using the software and is a security threat.

General Problems/Bugs

#5 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 SOAP Service does not omit log

Description

Comment

#4 SOAP Service does not return data

#6 Owner, Controlbody and other Groups of Register cannot be changed

Description

• No changes to rights on a register possible

Comment

#7 Development Container Environment needed

Description

Comment

Documentation

#3 SOAP Service does not omit log

Description

• Documentation doesn’t match with actual procedures, especially in installation and data migration
• Front-end not documented

Template

#3 Template

Description

Comment

Prioritization

• Capacities?

Next Steps

• JRC?

Issues