Escalating Technical and Project Instruction Issues
Idea: Develop a system where the user can be assured that these types of issues go directly to the responsible departments.
IT Technical issues:
Currently there are several reports of problems with Apple I-pads being reported from various sources. In the past, IT engineers could actively communicate with users to resolve these issues pretty quickly. I know because as a Mac user when I reported problems there were times that IT emailed me directly. When they received the proper communications, were able to investigate via a video or conversation, and could replicate the errors it seems that issues were taken care of a lot more quickly.
With this new Community, repeated advice to "clear the cache, delete cookies, and spin the ipads around" just don't seem to be cutting it. If the engineers are working on this, then perhaps a pinned post from the IT department in the Indexing group would be helpful: Currently Known Problems With Web-Indexing.
Project Instruction Errors:
I have spent way too much time writing several lengthy posts explaining why the Project Instructions on the Australian Will Project Part B project are either incongruent or incorrect. Part A was not great, but, Part B is just wrong. Apparently changes were made, but, they still make no sense. Not only to me, but, to others working on this project. Perhaps a system could be developed to take out the "middleman" (moderators) and allow us an avenue to get these findings directly to "headquarters". It doesn't happen that often where there are glaring errors in the project instructions so having one person to report them to, or a separate community Q&A with ONLY one or two moderators, could make a huge difference without being overwhelming.