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

RFC: Publishing record notes #642

Open
JoshuaCarroll opened this issue Jul 20, 2020 · 1 comment
Open

RFC: Publishing record notes #642

JoshuaCarroll opened this issue Jul 20, 2020 · 1 comment
Labels

Comments

@JoshuaCarroll
Copy link
Member

JoshuaCarroll commented Jul 20, 2020

Is your feature request related to a problem? Please describe.
Sometimes there are notes placed, either by the coordinators or by the repeater trustee, in the repeater's record that may be relevant to other operators.

For example, last year several repeaters in Malvern were taken off the air because the city decided to sandblast and repaint the water tower on which they were installed. This was, of course, temporary and was no fault of the repeater owners. So we have been working with them and giving them a fair amount of latitude as they mitigate the expenses involved in getting their repeaters re-installed and operational. Over the past few months several people have used the ARC website to report these same repeaters as off-the-air, which is good (we encourage people to do this as it helps us keep updated records) but if the notes of these repeaters were public they could have seen why those repeaters were unavailable and that we have been in frequent communication with the trustees in that area.

The only possible downside would be that these notes have been private (viewable only by coordinators and the repeater's trustee) up until now; so someone might have entered a note they expected to be kept private.

Describe the solution you'd like
I am suggesting that we make these, currently private, notes available to the public.

Describe alternatives you've considered
The only alternative would be to continue keeping these notes private.

Additional information
For an example, here are the notes for the 443.2 (N5CG) repeater in Little Rock:

7/20/2020 10:36:14 AM - Joshua Carroll (AA5JC)
• AdditionalInformation was changed from `` to Allstar node 49960

3/7/2020 10:25:13 AM - Joshua Carroll (AA5JC)
Just demonstrating. Repeater is fine.
• Status was changed from Suspected off-the-air to Operational

3/7/2020 10:23:52 AM - Joshua Carroll (AA5JC)
Repeater reported to be off-the-air

1/14/2019 8:48:47 PM - Joshua Carroll (AA5JC)
• TrusteeID was changed from 196 to 2
• TrusteeCallsign was changed from K5TEL to n5jlc

9/5/2018 10:31:22 AM - Joshua Carroll (AA5JC)
• SiteName was changed from Shinall Mountain (the tall one) to Shinall Mountain

9/1/2018 8:51:01 PM - Joshua Carroll (AA5JC)
• TrusteeID was changed from 2 to 196
• TrusteeCallsign was changed from N5JLC to K5TEL

9/1/2018 2:01:55 PM - Joshua Carroll (AA5JC)
• SiteName was changed from Shinall Mountain to Shinall Mountain (the tall one)

3/20/2018 7:00:00 PM - Robert King (W5LVB)
Transfer of system previously owned by Randy Wright KB5ZZI in LR.

3/20/2018 7:00:00 PM - Robert King (W5LVB)
Transfer of system previously owned by Randy Wright KB5ZZI in LR.

3/20/2018 7:00:00 PM - Robert King (W5LVB)
Transfer of system previously owned by Randy Wright KB5ZZI in LR.

@JoshuaCarroll
Copy link
Member Author

I guess no one cares. Publishing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant