Closed squidgetx closed 1 year ago
We want per column metadata (property and type in the example below) to be returned in the json response (#2)
"url" : { "property" : "https://schema.org/url", "type" : "https://schema.org/URL", "value" : "https://library.frick.org/permalink/01NYA_INST/1qqhid8/alma991000000019707141" }, "title" : { "property" : "http://purl.org/dc/elements/1.1/title", "type" : "xsd:string", "value" : "Bibliographie zur kunstgeschichtlichen Literatur in ost- und südosteuropäischen Zeitschriften." }, "relation" : { "property" : "http://purl.org/dc/elements/1.1/relation", "type" : "xsd:anyURI", "value" : "https://ark.frick.org/ark:37624/an1abc123", "label" : "Frick Auction Catalogs" }, "source" : { "property" : "http://purl.org/dc/elements/1.1/source", "type" : "xsd:anyURI", "value" : "https://yamz.net/term/ark/h3886", "label" : "null" }
The property and type fields are static per column. Maybe we just put this in a config somewhere and pull from it? Don't see a huge need to make it part of the DB
We want per column metadata (property and type in the example below) to be returned in the json response (#2)
The property and type fields are static per column. Maybe we just put this in a config somewhere and pull from it? Don't see a huge need to make it part of the DB