Project

General

Profile

Bug #5362

Create a GUI so user can easily archive a senosr's data from a dataturbine to a metacat

Added by Jing Tao over 8 years ago. Updated about 7 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
sensor-view
Target version:
Start date:
03/31/2011
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5362

archivingMenu.png (112 KB) archivingMenu.png Jing Tao, 03/31/2011 04:55 PM
scheduler.png (141 KB) scheduler.png Jing Tao, 03/31/2011 04:56 PM
archivingMenu.png (112 KB) archivingMenu.png Jing Tao, 04/04/2011 04:15 PM
sensor-scheduler.tiff (26.8 KB) sensor-scheduler.tiff Daniel Crawl, 04/19/2011 03:49 PM
archivingMenuItemOnToolMenu.png (114 KB) archivingMenuItemOnToolMenu.png Jing Tao, 05/05/2011 04:47 PM
sensorsInTable.png (30.9 KB) sensorsInTable.png Jing Tao, 05/05/2011 04:49 PM
sensorsInTable.png (30.8 KB) sensorsInTable.png Jing Tao, 05/05/2011 05:23 PM
sensorsInTable.png (76.4 KB) sensorsInTable.png Jing Tao, 05/09/2011 05:42 PM

History

#4 Updated by Daniel Crawl about 8 years ago

Here's my idea for the UI. After discussing with Jing and Derik, it may be difficult to populate since it's not easy/efficient to search for the kar files.

#5 Updated by Jing Tao about 8 years ago

Hi, matt:

Derik, Dan and I talked about the issue couple times. We've had to drop the idea of a new Sensor actor context menu for archiving, and a visual indicator on the Sensor actor that shows it's being archived.

Here are two options we've come up with:

Options 1. Add a menu item named "Sensor Archiving..." in the Tools menu. This action will bring up the GUI shown in the attachment (dan did it).

a. Filling this GUI involves these actions: search kar files in a remote data repository which archives the data from specified sensor; search existing schedules for the given kar file id in a scheduler server.

b. Clicking OK button will involve these actions:
) If there is no existing kar file associated with the sensor, the action will edit the archiving workflow by passing sensor id, DT server address, and dataset destination parameters to it. Then the customized kar file is uploaded to a remote repository.
) Save the changes of the schedule into a scheduler server

c. Clicking Cancel button will close the GUI

pros:
*) easy for user, user doesn't have to really know anything about the archival WF

cons:
) user doesn't know anything about archival WF :) -- conceptual disconnects: streaming data shown in site layout vs where the data actually comes from for archival (DataTurbine). Unclear when data being archived starts (beginning
of time of channel in DT). Auto-scheduled workflow kars are generated but user doesn't know their names.
) we're giving the archival WF special status and tying it to this specialized scheduler dialog (dialog needs certain wf
params to exist). However a user might want to archive with their own workflow, in which case they must learn how
to use the regular scheduler instead of this dialog.
*) 2 interfaces to scheduler from within kepler could be confusing

Option 2 No new features. User must simply edit the archival workflow and schedule it. We could simply add a small
annotation on site layouts "To archive this data, open sensor-view/archivalWorkflow.kar". The archive WF
could in turn have a small annotation explaining how to configure and schedule it "Tools=>Scheduler".

pros:
) no new work
) avoids all cons of (1)

cons:
) user must search use scheduler to check for pre-existing scheduled archival workflow themselves
) less 'guided' - user must open WF and config it themselves. User may find it is not easy to find a sensor id.

#8 Updated by Matt Jones about 8 years ago

Jing -- when creating dialogs, note that the Cancel button should be on the left, not on the right.

#9 Updated by Jing Tao about 8 years ago

Matt:

here is what i found online: *********************************************************
For Windows

Present the commit buttons in the following order:
  • OK/[Do it]/Yes * [Don't do it]/No * Cancel * Apply (if present) * Help (if present)

So Cancel is always on the right of OK button.

For MacOS

A button that initiates an action is furthest to the right. The Cancel button is to the left of this button.

So for MacOS users Cancel is on the left of OK button.

For other systems see guidelines.

Since my mock-up was done on MacOS, you are right, the cancel should be on the left side. Thanks!

#10 Updated by Jing Tao about 8 years ago

Move the "Cancel" button to the left side of the commit button.

#12 Updated by Derik Barseghian about 7 years ago

Jing notes there are some problems with the original design that need to be fixed. This will likely not ship in first sensor-view release.

#13 Updated by Jing Tao about 7 years ago

The menu for this action wasn't added to kepler, so we don't need to remove it.
The code for this feature locates sensor-view/src/org/kepler/sensor/archiveWorkflowScheduler

Here are more works we need to do:
1. Redesign the gui to show the existing schedules for sensors.
2. Create a mechanism to figure out if there is a existed kar file for archiving a specific sensor in the remote repository.

#14 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 5362

Also available in: Atom PDF