FCS Taskforce Video Conference 2014-03-04

• What?
  • FCS specification draft
• Who?
  • Members of the FCS taskforce
• When?
  • 4 March 2014: 14.00 - 16.00 CET
• Where?
  • FlashMeeting: ​http://fm.ea-tel.eu/fm/29d4d5-36470

Agenda

• Welcome
• Introduction round
• Discussion of the FCS specification draft
• Planning on time-frame for finishing the draft

Outcome: Decisions and Actions

• Action: add default recommendation for hits granularity: change wording to make clear that, Endpoint shall provide one hit within one <sru:record>. If multiple hits occur within one resource, and endpoint must serialize each hit as an individual record. Endpoints are expected to do this on best effort basis.
• Action: separate Data Views from Core-Spec; add them in an appendix, if a "one document" spec is compiled. Generic Hits however will also stay in Core-Spec, because it's the lowest common denominator.
• Action: change wording to indicate, that <Hits> element is optional, but make clear that Endpoint should use it
• Action: change wording to indicate,that an Endpoint MUST support Endpoint Description in explain
• Action: change element names <Collection*> to <Resource*>; that's more coherent with the other parts of the spec.
• Decision: drop recursive <Resource>; Endpoint Description (and/or CMDI Data Views) can be used to exploit Resource hierarchy
• Decision: submit new FCS spec to SCCTC for their April meeting; we need to be done with out work by end of March.
• Decision: incorporate discussed changes ASAP and start new (mail) discussion round
• Decision: Transition to new spec: build second Aggregator, that supports new spec; set deadline for centers with "old Endpoints" to adopt to the spec until 2014-10-31; the old Aggregator will be disabled in November; Tübingen will ensure, that they have a person to work on the Aggegator after May 2014.

Documents

• FCS specification draft