OAI-PMH Support (UXPROD-993)

[MODOAIPMH-13] OAI-PMH: Backend Configuration Created: 28/Sep/18  Updated: 16/Mar/20  Resolved: 20/Nov/18

Status: Closed
Project: mod-oai-pmh
Components: None
Affects versions: None
Fix versions: 1.0.0
Parent: OAI-PMH Support

Type: Story Priority: P3
Reporter: Hkaplanian Assignee: Aliaksandr Pautau
Resolution: Done Votes: 0
Labels: epam-thunderjet
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UXPROD-350 OAI-PMH Support Closed
relates to MODOAIPMH-95 Spike: Configuration properties analysis Closed
relates to MODOAIPMH-62 OAI-PMH: Backend Configuration - stor... Closed
Sprint: oai-pmh - sprint 50, oai-pmh - sprint 51
Story Points: 3
Development Team: Thunderjet
Epic Link: OAI-PMH Support

 Description   

Currently various system properties are used to specify runtime configuration. If a property is specified a hardcoded default is used.

This story builds upon that allowing for tenant-specific, modifiable values to be used.

  • Use mod-configuration (see API docs and other modules for examples - this is a widely used module)
  • Values from mod-configuration are used if present, System property values are used as a fallback. Hardcoded defaults are only used in cases where values aren't present in mod-configuration or specified via system properties.
  • UI work is outside the scope of this user story. Setting configuration via the mod-configuration API is acceptable for now.

Special cases:
There are some special cases that we'll need to address. These will be addressed in separate stories. For example, resumptionTokens may need to be invalidated if/when some config values change.


Generated at Fri Feb 09 00:13:42 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.