I haven't dug into the code any deeper, but I have discovered that if I enable org.dspace.identifier.VersionedHandleIdentifierProvider instead of
org.dspace.identifier.VersionedHandleIdentifierProviderWithCanonicalHandles in dspace/config/spring/api/identifier-service.xml The metadata is created and added to the metadatavalue table as expected. Is this the intended behavior? Off the top of my head, I would think that since versioning only applies to items, these classes should treat communities and collections the same regardless of which one is enabled. ~~Bill On Mon, Jul 15, 2024 at 4:41 PM DSpace Technical Support < [email protected]> wrote: > Hi Bill, > > I just tried this out on a DSpace 7.6.2 instance locally that I started > using the Docker scripts (documented at > https://wiki.lyrasis.org/display/DSPACE/Try+out+DSpace+7) > > I had no issues creating a new Community and Collection and both received > a new "dc.identifier.uri" which is displayed on the Community / Collection > Homepage next to the text saying "Permanent URI for this > [community]/[collection]". So, I don't believe this is a bug in > out-of-the-box DSpace 7.6.2. (That said, if others can confirm this same > behavior, then we can dig further to see if there are specific scenarios > where this might be happening) > > It's very odd to me that you'd see no errors when following the > Troubleshooting Guide steps > https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove). > You could verify that no errors appear in any of the tabs in your Browser's > DevTools (especially also the "Network" tab). > > Hopefully, if someone else runs into this they will mention it here as > well. > > Tim > > On Thursday, July 11, 2024 at 9:57:41 AM UTC-5 [email protected] wrote: > >> In DSpace 7.6.2, newly created collections and communities are not being >> assigned a persistent identifier (dc.identifier.uri) in the metadatavalue >> table. I have handle.canonical.prefix and handle.prefix set in dspace.cfg, >> and the correct metadata *is* generated for new items. There are no >> errors in any of the log files (apache, tomcat, dspace), nor in the >> javascript console. Setting the log level to DEBUG exposes other >> "org.hibernate.SQL >> @ insert into public.metadatavalue()" statements for community title, text, >> news, etc, but nothing for dc.identifier.uri >> >> As I said, this metadata is generated for all new items. >> >> Is anybody else seeing this issue or is this behavior configurable and >> 'off' by default or do I have some other isolated problem? >> Regards, >> Bill >> > -- > All messages to this mailing list should adhere to the Code of Conduct: > https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx > --- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/dspace-tech/74514521-fac0-4e5a-a0d4-d6461c4236a8n%40googlegroups.com > <https://groups.google.com/d/msgid/dspace-tech/74514521-fac0-4e5a-a0d4-d6461c4236a8n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- ______________________________________ Bill Tantzen University of Minnesota Libraries 612-626-9949 (U of M) 612-325-1777 (mobile) -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CADgrb7HGerDBdrRhWxMCj3bj5OHrxQXWkHNF9czmMRpKZsF9ug%40mail.gmail.com.
