Opened 9 years ago

Closed 9 years ago

#237 closed defect (fixed)

manage_data needs multiple select

Reported by: gegorbet Owned by: gegorbet
Priority: normal Milestone: future
Component: ultrascan3 Version:
Keywords: review Cc:


The us_manage_data application needs a multiple-select capability; and particularly needs the ability to delete a group of records with one action.

There are some ambiguities about the validity or meaning of certain actions on multiple records at different levels and from different sources. But there need to be some immediate changes for useability. These could start with the actions and combinations that are the least ambiguous.

Change History (4)

comment:1 Changed 9 years ago by gegorbet

  • Status changed from new to assigned

comment:2 Changed 9 years ago by gegorbet

After discussion and study, the proposed behaviors to be added to us_manage_data for both single and multiple selections are as follows.

  • Remove from DB involves API calls for only top-level records, since the delete APIs automatically remove descendants.
  • Remove from Local will include code to delete descendants of selected records, working from the bottom up, to avoid creating orphans.
  • Uploads will proceed (top-down) only if the Raw ancestor of each record is itself in the DB and each DB record is older than the local record.
  • Downloads will proceed (top-down) only if the Raw ancestor of each record is in the DB and a local Raw ancestor exists.
  • Actions involving Raw records will only directly act on the descendants of Raw records, leaving direct Raw record action to us_convert.
  • The "show details" action on multiple selections brings up a single dialog with summary information on all the selected records.

comment:3 Changed 9 years ago by gegorbet

  • Keywords review added

Multiple selection logic - as well as various other enhancements - have been added to us_manage_data. Behavior is now as documented in the last comment.


comment:4 Changed 9 years ago by dzollars

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.