Difficult to implement, but maybe we'll have to.
A complication is that a significant number of DNS updates are done by external automation (eg, hamnetdb). It (or at least its interface to the DNS robot) will have to change too. I don't know if the developers of that package are still active.
Perhaps this is the next thing for me to work on after the router settles down.
Thank you. - Brian
On Thu, May 11, 2017 at 01:48:52AM +0100, M6XCV (Mike) wrote:
Could I suggest a technical solution to a social problem?
You could add a column to the records table containing a username/id, default value NULL. You then add a way of specifying this field in the existing system.
You still have the existing system for managing records working exactly the same, however you now have the ability to assign ownership of new records (or existing ones) to a specific user. You could add a simple text field to the record editor to specify this.
Once records have a user associated with them you can provide whatever management interface is appropriate. If you wanted to let users create new records then ownership would be assigned at creation time.
An "ideal system" would allow multiple users to be associated with records, however I think that complicates things too much for this use case. Having records be editable by coordinators or their owner is probably sufficient functionality whilst keeping the old system unchanged.
In social terms: Adding self-service doesn't mean you have to get rid of all the checkouts and call-centres. It does reduce the workload, though. ;)
Thanks, Mike, M6XCV