Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to indicate a "Threatened" Headstone; Add #AtRisk term to ontology. #48

Open
Stephen-Gates opened this issue Apr 13, 2022 · 4 comments
Assignees
Labels
documentation Improvements or additions to documentation Missing Term

Comments

@Stephen-Gates
Copy link
Collaborator

In cemeteries, headstones can often be at threat of becoming Unserviceable. This is often due to trees growing in or near the grave and their roots or branches pushing over the headstone.

It is useful to indicate that a Headstone is "Threatened" so family, or others responsible for maintaining the grave site, can be contacted to take steps to avoid the headstone becoming Unserviceable.

Is a new status needed to indicate this status?

@rwarren2 rwarren2 added the documentation Improvements or additions to documentation label Apr 13, 2022
@rwarren2 rwarren2 self-assigned this Apr 13, 2022
@rwarren2
Copy link
Contributor

Unserviceable was originally meant for a thing that can no longer serve its purpose in terms of leaky roof, broken engine, etc...

What about #AtRisk as a term?

@Stephen-Gates
Copy link
Collaborator Author

I read Unservicable - The object is incapable of functioning but may be repairable, as applicable to a headstone. E.g. A headstone was toppled by a tree; has fallen and broken into pieces; is lying facedown so not readable; but is repairable.

State changes from Serviceable > AtRisk > Unservicable to potentially Ruins or, if repaired, Rebuilt (on a date), then Serviceable.

Is that the correct interpretation?

@rwarren2
Copy link
Contributor

rwarren2 commented Apr 18, 2022

I think that makes sense. I really had machinery in mind for Unservicable, but it still works for things like tombstones that are expected to be read. Let's go with it.

@rwarren2 rwarren2 changed the title How to indicate a "Threatened" Headstone How to indicate a "Threatened" Headstone; Add #AtRisk term to ontology. Apr 18, 2022
@Stephen-Gates
Copy link
Collaborator Author

Sorry I should have made this a discussion item. I've added some #49 use cases for headstone states in the discussion forum. It raises some questions about when the status should change from/to Un/serviceable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation Missing Term
Projects
None yet
Development

No branches or pull requests

2 participants