Uploaded image for project: 'DSpace'
  1. DSpace
  2. DS-1134

multilingual metadata for communities/collections

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 3.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Attachments:
      0
    • Comments:
      3
    • Documentation Status:
      Needed

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                helix84 Ivan Masár
              • Votes:
                5 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: