Log in

HCMC Journal

Configuring place elements for LINCS ingestion

: Martin Holmes
Minutes: 45

While we’re still in the dark with regard to what format LINCS wants our location data in, we do know that we need to move forward with a more elaborate setup for encoding location data, including recording various states, functions or usages of a location at different date ranges. For GitHub issue #3, I’ve now added the <state> element into the schema, constraining it only to the <place> element. I’ve also added a configured <valList> for the @ana attribute in the schema which is populated at schema build time from the location taxonomy values.