- setting maximum CMDI file size to 100MB (issue #275)
- upgrading to Spring Boot 3.4.1
- adding tests for curation-web module (issue #271)
- bug fixes
- make HTML reports callable with and without *.html suffix (issue #261)
- implementation of persistable cache manager ehcache (issue #262)
- removing file caches (issue #267)
- adding columns for public and CR residence in profile overview, profile detail view and collection's profile section (issue #264)
- adding score for uniqueness of MD selflinks to collection score (issue #265)
- removing link from profile overview to SMC browser (issue #266)
- making parallel processing for collection controllable again (issue #270)
- shifting scoring for CR residence from CMDI instance to profile (issue #272)
- bug fixes
- based on Java 21
- using virtual threads in collection processing (#228)
- improving accessibility of web-app (#249)
- sending accept header for outgoing http-calls (#250)
- processing accept header for incoming calls (#251)
- reducing calls to external services in maven tests (#244)
- using mock server for service tests (#234)
- adding functionality to delete outdated reports (#241)
- returning pre-generated profile reports in case of public profile validation (#258)
- bug fixes (#252, #256, #257)
- fix for rendering issue in tables (issue #245)
- adding back to current link in historic reports (issue #242)
- re-engineering exception handling to stop thread pool (re-opend issue #218)
- adding identification and timeout for schema look-up (re-opened issues #222, #231)
- allowing proxy usage for external HTTP calls (issue #227)
- sending User-Agent string with HTTP calls (issue #222)
- setting timeout for connection and reading (issue #231)
- making collection report history accessible (issue #233)
- adapting concept registry access
- upgrade to Spring Boot 3.2.2
- adding origin to duplicated mdSelflinks and rendering list in HTML view (issue #213)
- linking collection to VLO (issue #13)
- upgrade to Spring Boot 3.1.4
- adding robots.txt to CurateCtl to block bot access to /download and /record
- fix for issue #201
- adding robots.txt in curation-web (CurationCtl)
- allowing unzipped download for linkchecker details
- excluding non resolvable URN selflinks from link checking
- Refactoring of InstanceParser (issue #186) and InstanceFacetProcessor (issue #184)
- adding facet temporalCoverage in configuration (issue #180)
- adding functionality and view to see the latest link checker status results (issue #97)
- grouping link checking status details by URL (issue #162)
- adding unit tests for profile (issue #166) and CMD record (issue #167)
- dependency upgrades
- bug fixes
- bug fix for issue #160 and #162
- dependency upgrade of linkchecker-persistence to version 0.0.5
- converting the project to Spring boot project
- using Spring data JPA for persistence (see linkchecker-persistence, Spring caching and processor Beans)
- modularization of the project (app, web, shared api and services)
- reorganization of processors, sub-processors and reports
- separation of business-logic (in processors and sub-processors) and presentation layer (report instances)
- adding deactivation and deletion of non confirmed links
- externalising help and faq page as markdown
- renaming project to curation-dashboard, modules to curation-core and curation-web
- trimming of URLs for storage and look up
- new category »Invalid_URL« for URLs which can't be processed with Java URL class
- ordering link checking results in reports for severity (from »Ok« to »Invalid_URL«)
- calculate total linkchecker statistics from category statistics and overall from provider group statistics to prevent database access at different times while linkchecker changes data continuously
- upgrading RASA dependency to version 4.0.1
- upgrading RASA dependency to version 4.0.0
- various code changes because of changes in RASA API
- reviewing log levels