Per-resource maintainership metadata

[patcon]

This is pretty easy for us to fix ourselves, but might be nice if data "trickled" from organization to dataset to resource unless overridden. I'm encountering a situation where "Toronto Public Library" owns some datasets, but a citizen wrote scripts to convert the XML into JSON. Would be great if I could set the proper city contact info for the general dataset, but have the specific resource have it's own.

I suspect this isn't too common, but might become more common as that data portals become more participatory :)

[timwis]

Oh, I just replied to this in the gitter: am I oversimplifying it, or would putting "Maintained by XXX" in the resource's description property do the trick?

[patcon]

Just caught up on gitter! I'm personally not a fan of how unstructured the use of "description" would be, tbh

I'm now thinking that the approach that fits with the accepted portal data model would be to use isPartOf and reference the dataset that this new resource is derived from, so there would then be space in the new dataset object for full maintainer information

https://project-open-data.cio.gov/v1.1/schema/#isPartOf