Some thoughts about current and future work in nikita

[Aamot Software]

Hi,

Do you plan to optimize the web interface of Nikita for touch screens?

See https://jquerymobile.com/ for the framework and 
http://www.piperpal.com/mobile/ for my example.

Best,
Ole

Den 2023-07-12 14:25, skrev Thomas Sødring via nikita-noark:
> Hi,
> 
> During the spring semester, we spent a lot of effort on improving the
> Noark 5 API spec. Right before the summer, we launched a 1.1 version
> of the specification. That work was very enjoyable, and it highlighted
> the importance of getting nikita up to speed with the specification.
> 
> 
> Working on the nikita implementation to ensure we can be seen as a
> reference implementation is something I want to get into. There is not
> that much left to do for nikita to be a reference implementation, but
> I think the work is nitty-gritty work that is time-consuming.  I have
> also been thinking about what nikita needs going forward, and there is
> scope for some work to be done on the codebase. The most pressing task
> so far has been to get nikita up to Spring boot 3. We had some issues
> with the hibernate descriptions (inheritance) that was preventing us
> from being a Spring boot 3 application. These issues (expectedly) went
> away with the 3.1.1 version of Spring boot  so we are good to go.
> 
> Spring security in Spring boot 3 is updated and forces us to rethink
> our implementation of security.  I think we were due a revisit of this
> topic anyway, so it was coming, but we were forced to deal with it in
> the Spring boot 3 upgrade branch. We are moving to using keycloak as
> an SSO service for nikita. I think that is fine for anyone that wants
> to run nikita as a web-based service, but we see the scope and need
> for nikita to be able to run as a stand-alone system for an individual
> that want to be in control of their own record-keeping. I am not happy
> with the keycloak requirement and will look closer at how we can also
> run nikita without keycloak.
> 
> Looking at these issues makes me want to refactor the codebase a bit.
> I think the codebase is overly complex and could be tidied to make it
> easier for anyone else wanting to explore/understand the codebase. I'd
> guess there are some redundant classes and code in there now as well.
> 
> Going forward, I think we need to revisit the concept of DTO (data
> transfer object) that can give more control on what is returned to a
> client. We do not really have screening implemented properly in
> nikita. But to get that done properly, we likely need to have a better
> understanding of roles. In general, the concept of screening deserves
> its own research project to explore and understand what it entails.
> 
> I also think the import issue really should be dealt with. Being able
> to import data preserving the original systemID and timestamps is
> important. It is more a limitation of Noark rather than nikita, but
> just, in general, lacks being explored.
> 
> As always, your opinions and thoughts are welcome on #nikita on oftc.
> 
> 
> Thomas
> _______________________________________________
> nikita-noark mailing list
> nikita-noark at nuug.no
> https://lists.nuug.no/mailman/listinfo/nikita-noark

-- 
Best,
Ole Aamot
Aamot Software Founder and Developer - aamotsoftware.com
www.gnomeradio.org www.gingerblue.org www.gnomevoice.org
004741732002