Relequestual

GA4GH Search - A path forward - 2019-05-08

(Original located at https://groups.google.com/a/ga4gh.org/forum/#!topic/ga4gh-discovery-search/8gjdZU0Atsc - Requires login)

Hi all,

I’ve been mulling over the events of Hinxton conference, and also those from the past few months.

Relequestual

Search API - RC 5 Retrospective

Preface

A retrospective is an agile process for continuous improvement of a team and their processes.

Firstly, thank you all for your contributions to the Search API specification, and those who spent much time leading up to the plenary implementing and raising questions! I know first-hand that open source work is hard, especially with a distributed team, committing time as and when they are able.

Thank you also to those who were able to attend the GA4GH plenary in Basel a while back. We had some great discussions, and I feel I made some great connections across other workstreams and projects.

Relequestual

"questionA": {
      "type": "object",
      "properties": {
        "answer": {
          "type": "string",
          "minLength": 1,
          "enum": ["Yes", "No"]
        }
      }
    }

Relequestual

GA4GH Search API Proposal - Components

Executive Summary

The Matchmaker Exchange API is a successful live operating system which has resulted in real world life altering discoveries. Work on the Matchmaker Exchange API has shown that, while meeting most of the limited MME use cases, a more generalised discovery based API needs to be flexible, extensible, and planned for long term use.

A new discovery search based API should be expected to be in use for a minimum two decades once operational.

Keeping the barrier to entry low while not compromising on utility is essential. Each implementation of the API should be able to update to newer versions of the API at their own pace, without compromising interoperability. Each data repository exposing its data must be able to use as much or as little data for searching and responding to requests, is key.

Relequestual

{
  "$schema": "http://json-schema.org/draft-06/schema#",
  "type": "object",
  "allOf": [
    {
      "$schema": "http://json-schema.org/draft-06/schema#",
      "$id": "http:/example.org/example.schema.json",
      "type": "object",
      "properties": {
        "type": {

Relequestual

//  BaseScene.swift
//  Hospital Demo
//
//  Created by Ben Hutton on 17/11/2015.
//  Copyright © 2015 Ben Hutton. All rights reserved.
//

import Foundation
import SpriteKit
import GameplayKit

Relequestual

PHP on Pow.cx

Install Pow

$ curl get.pow.cx | sh

Install PHP with MySQL

$ curl -O https://raw.github.com/gist/4129846/7ae1709453a8a19ce9c030bf41d544dd08d96d85/php.rb

$ mv php.rb brew --prefix/Library/Formula

Relequestual

Keybase proof

I hereby claim:

• I am Relequestual on github.
• I am relequestual (https://keybase.io/relequestual) on keybase.
• I have a public key whose fingerprint is C55E 97EB 864D 2984 91BE 35F2 476E C3A2 DB2A 4974

To claim this, I am signing this object:

Relequestual

{
  "type":"object",
  "$schema": "http://json-schema.org/draft-03/schema",
  "title": "MatchMakerExchange Search Request",
  "name": "MatchMakerExchangeSearchRequest",
  "required":true,
  "properties":{
    "id": {
      "type":"string",
      "maxLength":255,

Relequestual

• sign in with twitter
• import favourites
• email user when import complete
• view list of favourites
• view all faves with images
• view all faves with/out links
• archive fave (de faves but kept on site)
• search faves
• search faves linked pages (so when import, save a cache of the article content or link included)
• order by date