I'd like to discuss how to integrate secretary workbench with the roster emeritus process that now is in production.
To recap: members who wish to go emeritus either - navigate to the documents site, download, print, sign, scan, and email an emeritus request to secretary or -navigate to roster __self__ page, double click Member status, and click (request emeritus status) or - send email to secretary stating that they no longer have access to foundation records and wish to go emeritus The above results in a file being placed in documents/emeritus-requests-received which pends for 10 days. After 10 days, secretary navigates to roster/memberid, verifies that there is a valid emeritus request, double clicks on Member status and clicks (move to emeritus). While the above is ok, it might be useful for secretary to be able easily to tell that there is an emeritus request pending. So I'm proposing a change to workbench. High level view: the index page, in addition to displaying incoming messages, also displays emeritus requests that are pending. The request could be formatted thus: Timestamp From Subject <date of request> Full Name of Member <date of 10 days later> The <date of request> would be a link to roster/memberid that would display a new page, not the workbench page. The request could be displayed the next time workbench is refreshed following receipt of the request, or could be displayed only after 10 days have elapsed. The message.status would indicate the "message" is an emeritus-request-not-ready-for-processing or emeritus-request-ready-for-processing with an appropriate visual cue. There is enough information available from svn to calculate the dates: %svn list --verbose emeritus-requests-received/clr.txt 56601 clr 4413 Jul 10 2020 clr.txt Timestamp From Subject Jul 10 2020 Craig L Russell emeritus rescission period ends Jul 20 2020 After secretary processes the request, closing the window would return to the secretary workbench. WDYT? Craig L Russell c...@apache.org
