Spring 2011 Goals and Tasks

This page is a bit out of date

We have not been updating this too much anymore. For a better idea of what tasks are currently outstanding, see the issues page. For an overview of what tasks have been accomplished, see the commits page (be sure to browse all branches). Our high-level goals have not changed, and can still be found below.

---

Below are high Level Goals for the semester (with tasks underneath):

*(Group) means whoever the information is relevant to, not necessarily the entire group.

• Level 1:
  • Audio organization page is fully functional
    • Markup:
      • (Amy) Finish wireframes of page [DONE]
        • (Group) Discuss wireframes and functionality to update everyone [DONE]
        • (Amy) Create HTML structure/CSS layout for audio page
          • (Group) Discuss HTML structure of waveform viewers [DONE]
            • (Amy) Create HTML structure and CSS layout for waveform viewers [DONE]
        • (Craig) Create first design mockup of UI [02/10/11]
          • (Group) Discuss design mockup and improvements/changes [DONE]
        • (Craig) Create mockup of segment/files panel [02/17/11]
      • (Group) Discuss color schemes [DONE]
        • Notes on color scheme are here.
      • (Chris) Develop icon set mockups [02/10/11]
      • (Chris) Develop revised icons [02/17/11]
      • (Chris) Upload icons as individual files to Google Docs, and link to on Icons document [02/24/11]
      • (Chris) Try out waveform icon [02/26/11]
      • (Chris) Small modifications to icons mentioned in email [03/03/11]
      • Icons
    • Backend:
      • (Adam & Colin) Discuss REST architecture [DONE]
        • (Adam) Implement the ability to manipulate tags through REST and test through unit tests [DONE]
        • (Adam) Implement the ability to manipulate audio objects through REST and test through unit tests [DONE]
        • (Adam) Implement the ability to manipulate audio segments and test through unit tests [02/13/11]
        • (Adam) Figure out how to manipulate nested resources to address issue covered in blog post [02/13/11]
      • (Someone) Add a date modified field to an audio segment so we can keep track of the most recent segments in a collection
      • (Someone) Add a “date_recorded” field to an audio file so we can keep track of when the file was recorded.
        • (Someone) Add a “date recorded” field to the audio upload form so we can allow the user to change the date. We can by default fill this with the date recorded, date modified, or current date. HTML5 has a date picker widget.
      • (Colin) Look into django-tagging or other related libraries for handling tags so we don’t have to. (Our tagging will work best for now)
      • (Colin) Change waveform image color to conform to Craig’s color scheme
      • (Colin) Change waveform overview image width
      • (Colin) Change waveform detail image height/resolution
    • Frontend:
      • (Colin/Amy) Determine how to organize views [02/09/11]
      • (Colin) Get model managers up and running [02/18/11]
      • (Colin) List audio files in audio panel [02/18/11]
      • (Colin) Implement ability to select audio file [02/19/11]
      • (Colin) Display overview waveform when audio file is clicked
      • (Colin) Display detail waveform when audio file is clicked
  • Manage Collections page is fully functional
    • (Amy) Create HTML structure/CSS layout for settings page [DONE]
    • (Colin) Finish organizing models on frontend [DONE]
    • (Colin) Remove model method calls from REST api code (like this one) [DONE]
    • (Colin) Remove this line, just add admin to model in frontend, admin should be a required field on collection model. [DONE]
    • (Colin) Fix ability to join collection [DONE]
    • (Colin) Implement ability to revoke request [DONE]
    • (Colin) Fix ability to manage collection requests for admin collections [DONE]
    • (Colin) Make sure deleting a collection works
    • (Colin) Create “Create Collection Event” whenever a collection is created [DONE]
    • (Colin) Move collection request and accept to custom tastypie URLs so we send only one request for this action. [DONE]
    • (Colin) Put stuff back, custom URLs aren’t going to work out [DONE]
    • (Colin) Figure out how to determine how m2m relationships have changed [02/17/11]
    • (Someone) Test user leaving collection. Authorization problem that can be solved with nested resources once Adam generalizes that
• Dashboard page is fully functional
  • (Amy) Create HTML structure/CSS layout for dashboard page
• Documentation
  • (Amy) Write user experience specification document [DONE]
• Level 2:
  • Color schemes developed & implemented
    • (?) Discuss and develop color scheme
    • (?) Implement in CSS
  • Buttons & icons developed and implemented
    • (?) Discuss and develop “Concert” logo
  • REST Permissions work properly
    • (?) Figure out tastypie issues and where these checks should go. (Colin has emails)
      • Relevant thread here
• Level 3:
  • Pretty start page with information about application
    • (?) Write content for start page
    • (?) Design for start page
  • UI is reliably responsive
    • (?) Determine where loading notifications are appropriate
    • (?) Determine the best place for loading notifications in the markup of each situation
    • (?) Determine how to organize loading notification code