Closed eric-jahn closed 10 years ago
In my experience with large public agencies, the "resource specialist" may be a person with long tenure at the agency, but who may not have any technical expertise regarding information technology issues. In those situations the "resource specialist" works with the person who performs that technology function.
This field, if I understood the conversation with the AIRS people and their member resource specialists correctly, is to indicate who is responsible for posting this information, and who could potentially correct or update it.
related to https://github.com/airs-linked-data/lov/issues/12 . I added the resource specialist's contact email () for making the change, and also left a field for the name of the resource specialist as well. So we're back to a vcard, which is the best solution, because it lets agencies post whatever they want people to know about the resource specialist's contact information (email or whatever way to contact them, even a web url for feedback).
changed in v0.0.10 with 5a893dc
attributesResourceSpecialist (a string with the name of the resource specialist) should have the email address of the place to contact if you have any questions about this data element. [Eric question] But will this eliminate accountability for this resource update? Can we have both?