Proposal Metadata Options

From Audacity Wiki
Revision as of 19:50, 10 February 2018 by Cliff Scott (talk | contribs) (The Problem)
Jump to: navigation, search
Proposal pages help us get from feature requests into actual plans. This page is a proposal to ...
Proposal pages are used on an ongoing basis by the Audacity development team and are open to edits from visitors to the wiki. They are a good way to get community feedback on a proposal.

  • Note: Proposals for Google Summer of Code projects are significantly different in structure, are submitted via Google's web app and may or may not have a corresponding proposal page.

The Problem

When opening an Audacity project that has existing metadata the default metadata template, if it has data in fields that are unused in the existing metadata, fills in the corresponding fields in the project metadata. This can result in unwanted data being added to the existing metadata.

Proposed Feature

In discussion with Paul, we propose to:

1. Change the default metadata behavior to cause the default metadata template data to be automatically merged only in the case of a new project.

2. Add a Merge button to the Edit Metadata dialog which would enable the user to "merge" the default metadata data into an existing project as it does now.

Note: When opening an existing project with existing metadata no change would be made to that metadata unless the user chose the "merge" option.

Developer/QA Backing


Use Cases




GUI Examples


Previous Feature Requests relating to this proposal