Skip to content

Need a single editable field in Provenance if possible #44

Description

@jdanish

For the Spring implementation, we just need one editable provenance field. The rest can remain TBD for refactoring. Otherwise we can't pilot the idea.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions