[
https://jira.duraspace.org/browse/DS-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart Lewis reassigned DS-700:
-------------------------------
Assignee: Kim Shepherd (was: Stuart Lewis)
> Bulk Metadata Editing: defining "formats" for export/re-import of selected
> fields
> ---------------------------------------------------------------------------------
>
> Key: DS-700
> URL: https://jira.duraspace.org/browse/DS-700
> Project: DSpace
> Issue Type: Improvement
> Components: DSpace API, JSPUI
> Reporter: Christophe Dupriez
> Assignee: Kim Shepherd
> Priority: Major
> Attachments: vancouver.csv
>
> Original Estimate: 16 hours
> Remaining Estimate: 16 hours
>
> When looking at use cases like:
> 1) bulk correction of keyword assignment (export existing indexation and let
> indexers create a new one using global search and replace)
> 2) translation of abstracts (export existing abstracts in different languages
> and let translators complete it and reimport)
> 3) export of records for merging in a word processor template
> current CSV Bulk Metadata Editing has many good feature and may be a lack in
> terms of defining exports/reimport of a selection of fields.
> Another thing which surprises me is the use of item ID instead of handle to
> identify the records. But this may be due to conflicting use cases:
> 1) bulk reorganisation of handle assignment (IDs stay but handles may change)
> 2) move from one version of an instance to another (IDs change but handles
> stay)
> I would like to define different thing in accordance with community whims if
> possible:
> 1) FORMATS: each format would be a list of metadata fields+language to be
> exported.
> 2) Standardize output directories: using a configurable pattern in
> DSpace.CFG, the exported/imported files would be send to a directory
> structure made of the user name and the format. A timestamp and/or a name
> choosen by the user would be used as a file name. For instance,
> /users/~[user]/dspace/csv/[format]/[filename].csv could be such a pattern.
> Missing directories would be automatically created. One could define a
> pattern where filenames contain the format type also:
> /users/~[user]/dspace/csv/[format]/[format]-[filename].csv
> My proposal for Export Formats Configuration would be to add a subdirectory
> dspace/conf/bulkedit where format.csv files would each give the headers of
> the desired columns in the export files with this format.
> We could keep a format named "allfields" for the current behavior.
> Please let me know soon what you would like so I can propose a module in line
> with community wishes!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
