[
http://jira.dspace.org/jira/browse/DS-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Donohue reassigned DS-387:
------------------------------
Assignee: Tim Donohue
Discussion from Developers Meeting on Dec 9, 2009. Consensus was that the idea
is a good one for post 1.6.0, but that the patch should be updated to be a
little less invasive. Assigning this to Tim (myself) and will resubmit patch
for review.
[15:10] <jat_ysu> http://jira.dspace.org/jira/browse/DS-387 Add ability for
various Packager plugins to report their custom Options via command line
[15:11] <tdonohue> +1 (for those who didn't realize the Packagers all have
separate options which aren't really documented)
[15:12] <mhwood> We've gone RC1 -- should this wait? Why or why not?
[15:12] <mdiggory> +0 tim you submitted it, you commit it ;-)
[15:12] <lcs> 0 - it's an API change, ought to go in next release
[15:13] <tdonohue> lcs and mhwood - correct, should go in next release
[15:13] <mdiggory> API changes?... probibly should go in major release
[15:13] <mdiggory> note... because we froze prior to the rc candidate, doesn't
mean things should stay froze during preparation for the next rc or release...
[15:13] <lcs> it's (a) minor, (b) a clean addition, but it does affect any
packager plugins people have implemented.
[15:14] <ClaudiaJuergen> that's a big but
[15:14] <mdiggory> thus the importance of doing it in a major release
> Add ability for various Packager plugins to report their custom "options" via
> command line
> ------------------------------------------------------------------------------------------
>
> Key: DS-387
> URL: http://jira.dspace.org/jira/browse/DS-387
> Project: DSpace 1.x
> Issue Type: Improvement
> Components: DSpace API
> Affects Versions: 1.5.2, 1.6.0
> Environment: Any command line interface
> Reporter: Tim Donohue
> Assignee: Tim Donohue
> Priority: Minor
> Attachments: PackagerOptions.patch
>
>
> Currently, the various packager plugins (METS & PDF) have no way to report to
> users what options are available to be passed to the plugin (via the
> 'packager -o [option]=[value]' flag).
> It'd be nice to allow a user to get a brief description of the valid options
> for each plugin via the commandline interface. I've implemented a simple
> patch (see attached) which lets users do this as follows:
> (1) running 'dspace packager -h' will output the normal Help information,
> including a list of all currently configured packager plugins (this feature
> already existed)
> (2) running 'dspace packager -h -t METS' will report normal Help information,
> but will *also* output some additional options which are specific to the METS
> packager plugin. Similarly, 'dspace packager -h -t PDF' would report any
> additional options which are specific to the PDF packager plugin.
> The way this is implemented is to add a "getParameterHelp()" method to both
> the PackageIngester and PackageDisseminator interfaces. Each implementing
> packager plugin is responsible for reporting any custom options in this
> "getParameterHelp()" method.
> See the attached patch for further details. (NOTE: This patch is very
> slightly dependent on DS-386 in that some of the line numbers in the patch
> are only correct if you already have installed DS-386.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
