Add new verbund ids to index #2365#2375
Conversation
ced15fe to
1a11a01
Compare
dr0i
left a comment
There was a problem hiding this comment.
Seems odd to me, see why e.g. at https://stackoverflow.com/questions/52845088/difference-between-keyword-and-text-in-elasticsearch ("text" vs "keyword"). I mean "id" feels like "keyword".
| "rpbId": { | ||
| "analyzer": "id_analyzer", | ||
| "type": "text" | ||
| }, | ||
| "schoeneNummer": { | ||
| "analyzer": "id_analyzer", | ||
| "type": "text" | ||
| }, | ||
| "hebisId": { | ||
| "analyzer": "id_analyzer", | ||
| "type": "text" | ||
| }, |
|
@dr0i I followed the examples in the index file 1 and 2. Also even if it is an id, the search is enabled e.g. with |
|
|
So question boils down to: "shall these IDs be case-sensitive or not" @fsteeg ? |
|
We decided to leave it as |
|
Deployed. Basedump-ETL started. To be reviewed tomorrow. |
@dr0i we need these ids for hbz/schlagwortfolgen-harvester#1
hebisIdwas already indexed, since it was introduced by @fsteeg in context of rpb.