Bug #1277

Descriptions for micro services should be dynamically received form the MCP server.

Added by Jesús García Crespo over 9 years ago. Updated over 6 years ago.

Status:NewStart date:
Priority:LowDue date:
Assignee:Mike Cantelon% Done:

0%

Category:MCP
Target version:-
Google Code Legacy ID:archivematica-622 Pull Request:
Sponsored:No Requires documentation:

Description

Descriptions for micro services are defined in their corresponding xml config file, and should be dynamically received from the MCP server. They are currently hard-coded in Django file settings.py. This should change to load from MCP.

[g] Legacy categories: Dashboard

History

#1 Updated by Evelyn McLellan about 9 years ago

  • Target version set to Release 0.8

Moving to 0.8 because there will be no 0.7.2 release.

[g] Labels added: Milestone-Release-0.8

#2 Updated by Jesús García Crespo over 8 years ago

  • Target version changed from Release 0.8 to Release 0.9

[g] Labels added: Milestone-Release-0.9
[g] Labels removed: Milestone-Release-0.8

#3 Updated by Jesús García Crespo over 8 years ago

[g] New owner: Mike Cantelon

#4 Updated by Courtney Mumma over 8 years ago

  • Subject set to Descriptions for micro services should be dynamically received form the MCP server.

#5 Updated by Evelyn McLellan over 7 years ago

  • Category set to MCP

#6 Updated by Courtney Mumma over 7 years ago

  • Target version changed from Release 0.9 to Release 1.0.0
  • Sponsored set to No

#7 Updated by Justin Simpson about 7 years ago

  • Priority changed from Medium to Low
  • Target version changed from Release 1.0.0 to Release 1.1.0

There are still micro service descriptions hard coded into the django settings module. This is not urgent, but it makes updating and changing workflows more difficult until this bug is resolved. Not sure if the dashboard should get the descriptions from the mcp server, or from the database. Db would probably be better.

#8 Updated by Justin Simpson over 6 years ago

  • Target version deleted (Release 1.1.0)

This change is not on our roadmap, unscheduling.

Also available in: Atom PDF