What is the best way to store/index a repository of PEPs?

[nleroy917]

@nsheff I've got a basic indexer working based on the pephub code and what we discussed in infrastructure meeting (05/23/2022). It spits out something like this:

changlab:
  pep_1:
    cfg: tests/data/ChangLab/PEP_1/TCGA_AllSamples_FinalBamList_config.yaml
    href: /pep/changlab/pep_1
    n_samples: 0
    name: PEP_1
  pep_2:
    cfg: tests/data/ChangLab/PEP_2/TCGA_AllSamples_FinalBamList_config.yaml
    href: /pep/changlab/pep_2
    n_samples: 796
    name: PEP_2
demo:
  amendments1:
    cfg: tests/data/demo/amendments1/project_config.yaml
    href: /pep/demo/amendments1
    n_samples: 4
    name: amendments1
  amendments2:
    cfg: tests/data/demo/amendments2/project_config.yaml
    href: /pep/demo/amendments2
    n_samples: 6
    name: amendments2
  append:
    cfg: tests/data/demo/append/project_config.yaml
    href: /pep/demo/append
    n_samples: 4
    name: append
.
.
.
geo:
  gse100494:
    cfg: tests/data/geo/GSE100494/GSE100494_samples.yaml
    href: /pep/geo/gse100494
    n_samples: 2
    name: GSE100494
  gse100750:
    cfg: tests/data/geo/GSE100750/GSE100750_samples.yaml
    href: /pep/geo/gse100750
    n_samples: 18
    name: GSE100750
  gse101426:
    cfg: tests/data/geo/GSE101426/GSE101426_samples.yaml
    href: /pep/geo/gse101426
    n_samples: 8
    name: GSE101426
  gse101512:
    cfg: tests/data/geo/GSE101512/GSE101512_samples.yaml
    href: /pep/geo/gse101512
    n_samples: 12
    name: GSE101512

You can then use the indexer to load an index file and just start serving with information.