Version 13 (modified by 13 years ago) (diff) | ,
---|
FCS Agenda
This is to collect ToDos? and Tasks regarding Federated Content Search.
1. Pin down the basic search-result format
The most urgent questions are:
- Do we agree on
<ccs:Metadata>
-element? - What sensible Resource(Fragment)-reference can we provide in
Resource@pid
ResourceFragment@pid
- Do we agree on
DataView[@type='kwic']
format (<kw>
-element)? - Can we have some kind of default string representation for every record, using
title
,name
or anything else that helps to identify the resource for the user? (I.e. PID is not very useful for this)
2. Specification of DataViews
In the next step we need a definition of the actual format of the individual DataView Types. This has to be harmonized with the work on Viewers. A separate page Viewable elaborates on this relationship.
Interested teams should take over individual types and lead working out a proposal. Tentative assignements:
- text, annotated text, written corpus, book
- Thomas@UniTueb; Matej@ICLTT
- list, matrix
- Thomas@UniTueb
- geolocation
- Marc@Meertens
Implement Search on Indexes
After the basic connectivity is established and simple queries can be submitted, the work shall be started on allowing to query specific indices. This involves solving the announcement of indices via explain/scan and correctly parsing the non-trivial query:
index relation searchTerm
Search context
Elaborate on ways of selecting a search context (Repositories/Collections/Resources to content-search in) either extensionally by providing a list of identifiers or intensionally by MD-query. See more on SearchContext and CDMDC.
Use cases
We need concrete scenarios to be able to check if what we do is any useful.
Further test Pazpar2
Assigned: Matej, ICLTT
There is a test-instance of PazPar2 running, that now can already connect to FCS-services. Currently main issue is Pazpar2 not being able to pass through XML-data inside the customizable fields.
Establish Repository Registry
For now we collect the information about existing services under RepositoryRegistry but this needs to be made a separate service.