Shared Quorum Archival Storage
Posted: Mon Jan 15, 2018 1:28 pm
I'm a recently called Stake YM Clerk and current EQ President (unusual, but it's a situational thing due to distance) and I have the same need for both callings. We have meetings and run events and then do event post mortems... all of which have a historical/archival value. The problem is... I have not been able to find a resource that would permit the storage of this information and continued access by members of those quorums as they change over time while barring those who no longer have those callings. Also, as has been noted elsewhere there is a potential security issue with such a resource, however, if the access could be controlled via the same mechanism (active directory?) used elsewhere on Church web sites and have users reminded on access that no confidential information is to be stored on the site... this security risk should be generally mitigated.
Having said that, is there existing or plans to add (or the capacity to create) small shared drives where Secretaries could put documents (Agendas, Meeting Minutes, Event Plans/Budgets and Event Post Mortems, possibly within those four directories) where access is provided by Church Calling and the information would persist over many individuals serving in those callings?
I'm asking because from my current investigations tools that currently exist will cause me to remain responsible for maintaining the resource long after I am released from the calling that I created it for. Transfers, generally, seem to be very difficult for them all and I'm pretty tech savvy.
Having said that, is there existing or plans to add (or the capacity to create) small shared drives where Secretaries could put documents (Agendas, Meeting Minutes, Event Plans/Budgets and Event Post Mortems, possibly within those four directories) where access is provided by Church Calling and the information would persist over many individuals serving in those callings?
I'm asking because from my current investigations tools that currently exist will cause me to remain responsible for maintaining the resource long after I am released from the calling that I created it for. Transfers, generally, seem to be very difficult for them all and I'm pretty tech savvy.