bug #6982: OriginalSource idNamespace + idInSource separator must be configurable - Edit - Redmine

bug #6982

OriginalSource idNamespace + idInSource separator must be configurable

Added by Andreas Müller over 1 year ago. Updated 26 days ago.

Status:

New

Priority:

New

Assignee:

Andreas Kohlbecker

Category:

cdm-dataportal

Target version:

Unassigned CDM tickets

Start date:

09/25/2017

Due date:

% Done:

Severity:

normal

Found in Version:

Description

der Slash in [Fig./1] steht nicht in den Daten, wo kommt der her?

Fig .1 ist in den Daten als "idInSource": "1", mit "idNamespace": "Fig." eingegeben. Bisher wird die idInSource immer mit einem Slash an den Namespace angehängt. Das ist offensichlich keine allgemein funktionierende Herangehensweise.

http://portal.cybertaxonomy.org/salvador/cdm_dataportal/media/fb52d954-f84b-450a-a57c-308f8a35a223

====

In the meanwhile we have changed the default separator from slash to space (#6815). But still configurability might be an issue.

Related issues

History

#1 Updated by Andreas Müller over 1 year ago

Copied from feature request #6815: OriginalSource idNamespace + idInSource default separator should be whitespace added

#2 Updated by Andreas Müller over 1 year ago

Andreas Kohlbecker wrote:

Regarding configurability: A simple default character would not be suffcient. Woul'nt we rather need a rule based approach? A cdm database may contains quite different identifiers types which need different formatting.

Two basic rules:

if idNamespace is a URI the separator is '/'

otherwise it is ' '

In general I agree, if this is easy enough to implement. Until now we did not have many namespaces being URIs. Implementing a simple character might be a first step and if we get usecases where this is not enough we might implement rules.

#3 Updated by Andreas Müller over 1 year ago

Tags deleted (~~salvador~~)

#4 Updated by Andreas Müller over 1 year ago

Andreas Müller wrote:

Andreas Kohlbecker wrote:

Regarding configurability: A simple default character would not be suffcient. Woul'nt we rather need a rule based approach? A cdm database may contains quite different identifiers types which need different formatting.

Two basic rules:

if idNamespace is a URI the separator is '/'

otherwise it is ' '

In general I agree, if this is easy enough to implement. Until now we did not have many namespaces being URIs. Implementing a simple character might be a first step and if we get usecases where this is not enough we might implement rules.

Maybe the rule could simply be that namespaces ending on "/" should not have a space while others need a space. Maybe there are also other characters that do not require a space.