Skip to content

Milestones

List view

  • No due date
    1/1 issues closed
  • This is a group of issues having to do with bug fixes, user-interface improvements, and enhancements for the Bulk Data Upload feature.

    No due date
    4/7 issues closed
  • Once we have upgraded to Rails 3.2, we can take advantage of the Rails Assets Pipeline. This will potentially make the Web site faster and will allow the use of more powerful Javascript and Stylesheet code.

    No due date
    1/1 issues closed
  • No due date
    5/11 issues closed
  • Once we have ensure that our data is consistent with the constraints we wish to add we can go ahead and add them.

    No due date
    20/21 issues closed
  • Once we have decided upon what database constraints we wish to have, even before we implement those constraints at the database level, we can ensure the the BETYdb rails app cannot perform any data insertions or updates that would cause a violation of those constraints.

    No due date
  • Required preparation varies by constraint type: Foreign-key constraints: * Non-Null: assign to an appropriate row, assign to a "catch-all" row, or delete row * Existing referent: Reassign or, if nullable, maybe set to NULL Uniqueness constraints: * Removed duplicate entries and update foreign-key references as needed. Value constraints: * Update invalid values, set to NULL (if nullable), or remove the row in which they occur Other?

    No due date
    2/5 issues closed
  • Make a list of all constraints the BETYdb database should satisfy. Related to Redmine issues: * https://ebi-forecast.igb.illinois.edu/redmine/issues/1915

    No due date
    2/3 issues closed
  • Generic for tasks related to uploading bulk data (including specific data sets that need to be uploaded)

    No due date
    3/8 issues closed