Project

General

Profile

Bug #4577

integrate, and separate from save/export, the code for Uploading

Added by Derik Barseghian over 9 years ago. Updated over 9 years ago.

Status:
New
Priority:
Normal
Category:
general
Target version:
Start date:
11/24/2009
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
4577

Description

1) There's UploadToRepository (module: repository), UploadKARToRepositoryNoGUI (provenance), and ComponentUpload (gui). Now that the code for exporting is more integrated, code for uploading should likewise be refactored to avoid duplication.

2) I also want to separate upload out of Save / Export actions. I find it annoying that if I have an upload repository enabled, I'm prompted for upload every time I Save Archive or Export Archive (from WRM), and I think it's confusing that a user who wants to upload a workflow from the File menu is supposed to use the Save Archive option. Let me know if you disagree...


Related issues

Blocks Kepler - Bug #4515: Finish and Document the Save/Open KAR file functionalityResolved10/29/2009

History

#1 Updated by Derik Barseghian over 9 years ago

A user can now create different types of KARs from within Kepler, and upload them to the repository via context menu from the component library. KARs can contain:
a) workflow
b) workflow, roml
c) workflow, roml, rio
d) workflow, workflowRun
e) workflow, roml, rio, workflowRun
f) actor

A user can't make these anymore, but this may be re-enabled at some point:
g) workflow 1, workflowRun 1, workflowRun 2
h) workflow 1, workflowRun 1, workflow 2, workflowRun 2
i) workflow 1, roml 1, rio 1, workflowRun 1, roml 2, rio 2, workflowRun 2
j) workflow 1, roml 1, rio 1, workflowRun 1, workflow 2, roml 2, rio 2, workflowRun 2
etc.

When uploading a KAR to Metacat, we upload the KAR as data, and any contained workflows and workflowRuns are also uploaded as metadata pointing to the KAR. This means that the component library upload code, which is in the gui module, needs a way to know what items serve as metadata for a KAR (and of course the other classes that do uploading need to know this as well). This leads me to think that karEntryHandlers should probably be putting an attribute into the Manifest like isMetadata: true.

Thoughts?

#2 Updated by ben leinfelder over 9 years ago

oh, I like that - then the gui code never needs to "know" all the different kinds of metadata entry types, just that they are indeed this metadata type.

#3 Updated by Derik Barseghian over 9 years ago

This bug is a more of request for refactoring and an RFE (when a remote repository is check-marked, don't always prompt to upload on a Save Archive).

The suggestion in comment#1 is no longer relevant since the KAR system's been redone and we're moving to kar-xml.

Retargeting to post 2.0.

#4 Updated by Redmine Admin about 6 years ago

Original Bugzilla ID was 4577

Also available in: Atom PDF