History:Next Generation Schema/Edit User Interface: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
(Questions for luks or acid2)
Line 40: Line 40:


12. Can an existing combo "artist thingie" get looked up, or does each part have to be looked up separately? (ie, looking up "Queen & David Bowie" as a single step, rather than having to look both "Queen" and "David Bowie" up separately).
12. Can an existing combo "artist thingie" get looked up, or does each part have to be looked up separately? (ie, looking up "Queen & David Bowie" as a single step, rather than having to look both "Queen" and "David Bowie" up separately).

13. Release and RG annotation and ARs are of course editable for existing releases, but would there be anything that would make it impossible to allow adding these as part of an overall release / RG add? ie, submitting the edits to add these as part of the batch of edits submitted to the server, with the server, as part of the edit batch processing, applying that new annotation and/or ARs to the just-created release or RG?

Revision as of 13:03, 22 July 2009

This wiki page aims to define the goal for the Edit user interface for NGS.

Goals

  • A release page has several "data" tabs. A new "edit" tab needs to be added that should be visually distinct from the other tabs. Perhaps even right aligned.
  • The existing "data" pages should not have any "edit" modifications.
  • The edit page should look nearly identical to the data page initially.
  • Mousing over the various elements should give a clue that an element can be edited.

Workflow

Any edit that a user starts, but does not submit, will be send to the server's "stash". If the user starts an edit and then navigates away from the page, the current changes should be submitted to the server stash transparently. Returning to that edit page should automatically retrieve the stashed changes from the server and load them into the page.

The user should also be able to get a list of stashed edits and be able to resume or delete any of them. A user can come back later and retrieve stashed edits to finish and submit them. Edits can be started on a mobile in a music store and retreived at a home computer later on to be finished and submitted.

Open Questions

These are questions I have run into, but don't yet have answers to, while working on the UI -BrianFreud

1. How to add a controller action, such that http://216.121.252.161:3000/release/ceffc5e5-ae9f-4d24-a8e7-8e22e89a5153/edit loads http://216.121.252.161:3000/release/ceffc5e5-ae9f-4d24-a8e7-8e22e89a5153 but with the variable "edit" set = 1?

2. How to get the list of countries, country abbreviations, and country values?

3. How to get the list of formats and format values?

4. How to get the list of scripts and script values?

5. How to get the list of types and type values?

6. How to get the list of statuses and status values?

7. How to get the list of languages and language values?

8. How to get the list of packagings and package values?

9. How to get the list of artist types and type values?

10. How to get the list of artist genders and gender values?

11. How to get the list of label types and type values?

12. Can an existing combo "artist thingie" get looked up, or does each part have to be looked up separately? (ie, looking up "Queen & David Bowie" as a single step, rather than having to look both "Queen" and "David Bowie" up separately).

13. Release and RG annotation and ARs are of course editable for existing releases, but would there be anything that would make it impossible to allow adding these as part of an overall release / RG add? ie, submitting the edits to add these as part of the batch of edits submitted to the server, with the server, as part of the edit batch processing, applying that new annotation and/or ARs to the just-created release or RG?