bug #6982: OriginalSource idNamespace + idInSource separator must be configurable - EDIT - EDIT Project Management

Custom queries

5.33
cdm-dataportal (open)
last 7 days tickets
mine in current release
phycobank
phycobank-index-closed
phycobank-registration-closed
potentially missed issues
recently updated
Release3.7
Release3.8
Release4.0
Release4.1
Release4.10
Release4.11
Release4.12
Release4.13
Release4.14
Release4.16
Release4.2
Release4.3
Release4.4
Release4.5
Release4.6
Release4.7
Release4.8
Release4.9
Release4.9
Release5.0
Release5.1
Release5.10
Release5.11
Release5.12
Release5.13
Release5.14
Release5.15
Release5.16
Release5.17
Release5.18
Release5.19
Release5.2
Release5.20
Release5.21
Release5.22
Release5.23
Release5.24
Release5.25
Release5.26
Release5.27
Release5.28
Release5.29
Release5.3
Release5.30
Release5.31
Release5.32
Release5.33
Release5.34
Release5.35
Release5.36
Release5.37
Release5.38
Release5.39
Release5.4
Release5.40
Release5.41
Release5.5
Release5.6
Release5.7
Release5.8
Release5.9
Remoting-Versions
Taxeditor-UX (Platform Etablierung)

Actions

Copy link

bug #6982

open

OriginalSource idNamespace + idInSource separator must be configurable

Added by Andreas Müller over 6 years ago. Updated about 5 years ago.

Status:

New

Priority:

New

Assignee:

Andreas Kohlbecker

Category:

cdm-dataportal

Target version:

Unassigned CDM tickets

Start date:

Due date:

% Done:

Estimated time:

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

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

Closed

Andreas Kohlbecker

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by Andreas Müller over 6 years ago

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

Actions

Copy link

Updated by Andreas Müller over 6 years 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.

Actions

Copy link

Updated by Andreas Müller over 6 years ago

Tags deleted (~~salvador~~)

Actions

Copy link

Updated by Andreas Müller over 6 years 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.

Actions

Copy link