Bug #1532


Add support for "cloning" packages to support content re-use

Added by Saurabh Garg over 19 years ago. Updated about 13 years ago.

morpho - general
Target version:
Start date:
Due date:
% Done:


Estimated time:


Add support for "cloning" packages to support content re-use (i.e. as
independent new packages, not existing package revisions)

Relevant part from Wade Sheldon's email...

"The only "problems" I had with the program were really ones of scope related
to using it within the context of an existing IM program in LTER or elsewhere
(the same issues I discussed with Chris and Chad years ago in Phoenix). Unless
I missed something big, your approach to working with metadata using Morpho
only allows two avenues for loading metadata documents: a) manual creation of
data packages de novo using forms and wizards, b) retrieval of existing
packages from Metacat. Because Morpho doesn't appear to offer any mechanism for
importing local metadata documents (i.e. eml files) in whole or in part, or
copying existing packages for editing and re-use for repeat submissions (i.e.
boilerplating or templating), there is no mechanism for coupling Morpho with
existing information systems or recouping effort already spent entering
metadata for long-term monitoring data sets (for which only temporal coverage,
abstract and title may have changed since the last submission).

I view this as a large impediment that may preclude use of Morpho in many IM
shops, at least for initial metadata entry and editing. In order to create
metadata more efficiently, many IMs will be forced to generate eml metadata for
new data sets via some other path that supports content re-use (e.g. raw xml
editing or generation from an RDBMS using scripting) and then load them into
Metacat via Harvester or another channel. This will limit use of Morpho to
metadata viewing/polishing and Metacat querying, which is a shame considering
all it has to offer users."

Actions #1

Updated by ben leinfelder about 13 years ago

In it's current incarnation, Morpho supports many features referenced in the note below. Here are the highlights:
-EML file import from local file system. EML documents need not only come from a Metacat server to be edited in Morpho now
-While there are no true "templates", we do support data package duplication (metadata) and data substitution. By either importing a 'tempate' EML file or retrieving one from a remote Metacat server, a user can duplicate that EML locally, attach their data file (assuming it matches the attribute definitions exactly), edit any boilerplate contact information or other metadata that needs updating and save. It's a fairly straightforward workflow for reusing existing data packages.

Actions #2

Updated by Redmine Admin over 10 years ago

Original Bugzilla ID was 1532


Also available in: Atom PDF