MCRURNGranularRESTService does not register urn for landing page after urn assignment

Description

Steps to repeat:

Configure service in mycore.properties:

  1. URN - PI settings

MCR.PI.Service.DNBURNGranular=org.mycore.pi.urn.rest.MCRURNGranularRESTService
MCR.PI.Service.DNBURNGranular.Generator=UUIDURN
MCR.PI.Service.DNBURNGranular.MetadataService=DNBURNGranular
MCR.PI.Service.DNBURNGranular.IgnoreFileNames=mets\.xml,alto/.+,tei/.+
MCR.PI.Service.DNBURNGranular.supportDfgViewerURN=true
MCR.PI.Generator.UUIDURN=org.mycore.pi.urn.MCRUUIDURNGenerator
MCR.PI.Generator.UUIDURN.Namespace=urmel-
MCR.PI.MetadataService.DNBURNGranular=org.mycore.pi.MCRPIXPathMetadataService

  1. Autostart
    MCR.Startup.Class=%MCR.Startup.Class%,org.mycore.pi.urn.rest.MCRURNGranularRESTRegistrationStarter

  • assign urn to derivate with: $.post("<host>/rsc/pi/registration/service/DNBURNGranular/<derivate-id>

  • if your derivate has 1 image you will see two entries in the MCRPI table with the 'registered' column set to a certain date. One shorter urn (should point to <host>/receive/<derivate-owner>) and one longer urn pointing to iview2

  • BUT: only the longer urn is actually registered (because the main urn is already set as registered)

  • if you then set the 'registered' column to null both urn are getting registered

Environment

None

Assignee

Huu Chi Vu

Reporter

Silvio Hermann

Labels

None

URL

None

External issue ID

None

Components

Fix versions

Affects versions

Priority

High
Configure