Skip to content

Multiple stages of policy definition/parameterization/configuration #22

@zyzzyxdonta

Description

@zyzzyxdonta

When discussing #16 today, it became clear that we're not quite sure yet, who get's to configure things. We came to the following conclusions:

  • Policy makers should be able to write policies and parameterize them. Parameters may have a default value but are not required to.
  • Dedicated personnel at institutions (e.g. librarians) should be able to bundle up policies and overwrite the defaults to make the policies work for their own institutions.
  • End users (i.e., people who run HERMES/Software CaRD to pulish their software) should be able to overwrite values, too, but it should be traceable when they did so to simplify curation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    SpecificationIssues related to the specification

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions