You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The global search makes it possible to search over all data model (rdm, marc21, lom) and maybe others (communities) too. app-rdm creates per default the /search as the rdm-records search. Which is normally perfect, but for that special case not good. The global search should be on /search and the special searches on special enpoints
/search -> global search (which is dublin-core) /rdm/search -> rdm-records /marc21/search-> marc21 /lom/search-> lom
Solution:
overwrite SEARCH_UI_SEARCH_TEMPLATE and create a new endpoint for rdm/search which uses the original value for SEARCH_UI_SEARCH_TEMPLATE
an overwriting of /records is maybe not necessary. this has to be tested. because it exists /search could then get the response from /api/dublin-coreand /rdm/search gets the response from /api/records
The text was updated successfully, but these errors were encountered:
The global search makes it possible to search over all data model (rdm, marc21, lom) and maybe others (communities) too. app-rdm creates per default the
/search
as therdm-records
search. Which is normally perfect, but for that special case not good. The global search should be on/search
and the special searches on special enpoints/search
-> global search (which is dublin-core)/rdm/search
-> rdm-records/marc21/search
-> marc21/lom/search
-> lomSolution:
overwrite
SEARCH_UI_SEARCH_TEMPLATE
and create a new endpoint forrdm/search
which uses the original value forSEARCH_UI_SEARCH_TEMPLATE
an overwriting of
/records
is maybe not necessary. this has to be tested. because it exists/search
could then get the response from/api/dublin-core
and/rdm/search
gets the response from/api/records
The text was updated successfully, but these errors were encountered: