Ticket #139 (new task)
Define initial ImportDef/ImportStatus types
| Reported by: | jmoore | Owned by: | brain |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | Import | Version: | 3.0-M1 |
| Keywords: | Cc: | brain, jmoore, callan |
Description
As a starting point for import work, there needs to be a couple database tables. The tiki import discussion provides a rough outline.
(10:40:47) chris: Status is one thing. Request for more information is another.
(10:41:48) chris: ie. 1 of these groups is missing files, want to tell me where they are?
(10:42:15) chris: Or this file is missing channel information, can you fill it out please?
(10:42:16) josh: k.
(10:43:01) chris: Essentially, dialog boxes that prompt for simple y/n questions and potentially some text fields.
...
(10:47:46) chris: Probably going to need at least four fields: int stage, int step, int total_steps, string message
(10:48:01) chris: Essentially for filling a progress monitor.
(10:48:25) josh: stage,step,total check. should message eventually be more structured?
(10:48:37) josh: message --> { files | channels | ... }
(10:48:39) chris: Potentially, yes.
(10:48:42) josh: ok.
(10:49:01) chris: It could be the type currently being worked on.
(10:49:10) josh: which type?
(10:49:13) chris: Channel, RenderingDef, etc. etc.
(10:49:15) josh: ok.
(10:49:16) chris: ome.model type.
(10:49:53) josh: stage, step, total, current_reference, problem_enum, message?
Change History
Note: See
TracTickets for help on using
tickets.
