Administrator Reports (Beta feature) is not turning on in Dspace Version 8

[sanjib modak]

According to the manual to turn this feature I edited the contentreport.cfg file and enabled the contentreport. like this "contentreport.enable = true" but still it is not turning on, I am not seeing any 'Report' menu in the sidebar of the UI although logged in with administrative privilege.  I am getting this error in the Dspace log file.  

"2024-07-30 11:28:43,986 INFO  68937693-3441-49a3-bd72-414718719508 92ef84cf-a2ad-4d4f-ac0b-7fe8498a681d org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request [GET /server/api/config/properties/contentreport.enable] originated from /
2024-07-30 11:28:43,999 WARN  68937693-3441-49a3-bd72-414718719508 92ef84cf-a2ad-4d4f-ac0b-7fe8498a681d org.dspace.app.rest.exception.DSpaceApiExceptionControllerAdvice @ An exception has occurred (status:404 exception: No such configuration property: contentreport.enable at: org.dspace.app.rest.repository.ConfigurationRestRepository.findOne(ConfigurationRestRepository.java:58))"

As it suggests there is no configuration property in rest.cfg file but i checked and it is there. 

"# Define which configuration properties are exposed through the http://<dspace.server.url>/api/config/properties/

# rest endpoint. If a rest request is made for a property which exists, but isn't listed here, the server will
# respond that the property wasn't found. This property can be defined multiple times to allow access to multiple
# configuration properties.
# (Requires reboot of servlet container, e.g. Tomcat, to reload)
rest.properties.exposed = plugin.named.org.dspace.curate.CurationTask
rest.properties.exposed = google.analytics.key
rest.properties.exposed = versioning.item.history.include.submitter
rest.properties.exposed = researcher-profile.entity-type
rest.properties.exposed = orcid.application-client-id
rest.properties.exposed = orcid.authorize-url
rest.properties.exposed = orcid.scope
rest.properties.exposed = orcid.disconnection.allowed-users
rest.properties.exposed = registration.verification.enabled
rest.properties.exposed = websvc.opensearch.enable
rest.properties.exposed = websvc.opensearch.svccontext
rest.properties.exposed = websvc.opensearch.shortname
rest.properties.exposed = websvc.opensearch.autolink
rest.properties.exposed = submit.type-bind.field
rest.properties.exposed = google.recaptcha.key.site
rest.properties.exposed = google.recaptcha.version
rest.properties.exposed = google.recaptcha.mode
rest.properties.exposed = cc.license.jurisdiction
rest.properties.exposed = identifiers.item-status.register-doi
rest.properties.exposed = authentication-password.domain.valid
rest.properties.exposed = ldn.enabled
rest.properties.exposed = ldn.notify.inbox
rest.properties.exposed = handle.canonical.prefix
rest.properties.exposed = contentreport.enable

rest.properties.exposed = duplicate.enable "

So if anyone has any idea regarding this problem please let me know as soon as possible.

[sanjib modak]

Just resolved the issue.. 

--
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 a topic in the Google Groups "DSpace Technical Support" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dspace-tech/I0qYVJHaUD4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to dspace-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/17f1f160-0ea3-42ec-8886-77b1d7c09c9an%40googlegroups.com.

[Mehmet Demirel]

How to resolved?

[Kalyan kumar]

Hi Mehmet ,

It looks like "contentreport.enable = true" will enable the API to provide the output, hence making the content reporting functionalities available through the DSpace REST API. This is different from directly "enabling the view of admin reports" in the user-interface.

Regards

Kalyan

Greenbooks Imaging Services LLP

On Tue, Mar 25, 2025 at 12:25 AM Mehmet Demirel <unib...@gmail.com> wrote:

How to resove?

On Thursday, 1 August 2024 at 16:19:57 UTC+3 sanjib modak wrote:

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 dspace-tech...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/d9d6f34d-5aa1-472e-82b7-e9d67a308e55n%40googlegroups.com.

[Michael Koch]

If you are on the 8.1 version (Tag in GitHub), there is one thing you have to do in the frontend code:

Either update src/app/menu-resolver.service.ts to the newest version in GitHub or add

this.createReportMenuSections(); in the function createAdminMenu$() in the same file.

That did it for me.

[Kalyan kumar]

Thanks @michael Koch. Will try.

Kalyan

Greenbooks

To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/e20057e2-e820-4925-a639-2e91329c8313n%40googlegroups.com.

[Mehmet Demirel]

Solved: I updated src/app/menu-resolver.service.ts in v8.x
this.createReportMenuSections();

https://github.com/DSpace/dspace-angular/blob/dspace-8_x/src/app/menu-resolver.service.ts