[
https://jira.duraspace.org/browse/DS-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Masár updated DS-1134:
---------------------------
Status: Volunteer Needed (was: Received)
> multilingual metadata for communities/collections
> -------------------------------------------------
>
> Key: DS-1134
> URL: https://jira.duraspace.org/browse/DS-1134
> Project: DSpace
> Issue Type: Improvement
> Affects Versions: 3.0
> Reporter: Ivan Masár
> Labels: i18n, metadata
>
> I suggest to allow community/collection metadata to be stored in multiple
> languages.
> The community/collection "Edit metadata" form would be similiar to item "Edit
> item > Item metadata" form - a third column with language code would be added.
> Problem:
> Almost all of DSpace interface can be localized - messages, emails, front
> page news, even item metadata can be in multiple languages and can be
> selected depending on the interface language - but community/collection
> metadata (including names) cannot, disrupting the fluent localized experience.
> Improvement rationale:
> 1) item metadata allows values in multiple languages
> 2) it would allow community/collection metadata to be displayed in current
> language (determined by browser content negotiation), i.e. the same language
> as the rest of the interface
> 3) even community/collection names should be localized (the unique identifier
> is handle, not its name)
> Improvement requirements:
> 1) This would require changing the "community" and "collection" tables -
> stripping them of other columns than "community_id", "admin" and
> "collection_id", "workflow_step_1", "workflow_step_2", "workflow_step_3",
> "submitter", "admin", respectively.
> 2) The stripped columns would be added as rows into 2 new tables, say
> "community_metadatavalue" and "collection_metadatavalue" modelled after the
> "metadatavalue" table. The relation between "community"/"collection" and
> "community_metadatavalue"/"collection_metadatavalue" tables would be the same
> as the relation of "item" to "metadatavalue".
> 3) A migration path would be needed to migrate data from current "community"
> and "collection" tables to the new "community_metadatavalue" and
> "collection_metadatavalue" tables.
--
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 Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
