[
https://jira.duraspace.org/browse/DS-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27406#comment-27406
]
Christophe Dupriez commented on DS-1367:
----------------------------------------
Either the community needs in the short term ItemBatchUpdate functions
PoisonCentre and WindMusic.org use intensively (100k records each, selected and
loaded those last 5 years) and the software behind this DIM can be merged in
DSpace. Or the community don't really need it rapidly...
If the community have needs, then how are they similar or different today from
what ItemBatchUpdate proposes since all that time?
My feeling is that either a committer feels it OK for immediate purposes nearly
"AS IS" or either the DIM should be rethought as a longer term "model" of a
DSpace record.
But can we agree on such a model? Where could we collaborate to it? Do we have
energies (time, money) to do that? Who takes a strong leadership on this?
> DIM schema
> ----------
>
> Key: DS-1367
> URL: https://jira.duraspace.org/browse/DS-1367
> Project: DSpace
> Issue Type: Task
> Affects Versions: 3.0
> Reporter: João Melo
> Labels: oai, validation
> Attachments: DIM.xsd
>
>
> My proposal:
> http://www.lyncode.com/schemas/DIM.xsd
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery
and much more. Keep your Java skills current with LearnJavaNow -
200+ hours of step-by-step video tutorials by Java experts.
SALE $49.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122612
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
