Closed giorgiosironi closed 4 years ago
Biochemistry and Chemical Biology
is in the service,Biochemistry and chemical biology
is in the XML, what should happen? Accepted and normalized, or error?
I would expect a slugified version of the subject
element value to determine what is distinct or not - in other words Biochemistry and Chemical Biology
and BIOCHEMISTRY AND CHEMICAL BIOLOGY
would be identical.
what value should show up in the frontend?
I see there being three options:
BIOCHEMISTRY AND CHEMICAL BIOLOGY
, slugified to biochemistry-and-chemical-biology
, and any ids with that value displayed as Biochemistry and Chemical Biology
)should these conventions be extended to e.g. article types?
It would make sense to use similar logic, I think, given that the data (XML) will be provided in the same format, and will bring the same challenges.
CC @Melissa37
I agree with what @FAtherden-eLife has suggested.
all caps, sentence case or camel case
Do you mean Biochemistry and Chemical Biology
as sentence case? There is no generic algorithm that I know of to reliably generate this from a lowercase version.
Do you mean Biochemistry and Chemical Biology as sentence case? There is no generic algorithm that I know of to reliably generate this from a lowercase version.
No, that's camel case (ie a camels hump goes up and down :-))
Sure, makes sense that it's input in defines that
Updated description with results from call today.
Implies to verify the behavior of filtering APIs on
scholarly-content-detail
.Scenarios
Biochemistry and Chemical Biology
is in thescholarly-content-detail
service,Biochemistry and chemical biology
is in the XML, what should happen? It should found with case-insensitive matching, and normalized to what is already in the service (Biochemistry and Chemical Biology
),See also https://github.com/microsimulation/ijm-xml/issues/151 where we try to avoid most of the inconsistency by making the typesetter fixing the XML before we use it. Can't guarantee we will always be able to do this.
/cc @FAtherden-eLife