My colleague and I are taking the lead on implementing data reviewer in our office. I've attended the ESRI training for Data Reviewer and found it immensely helpful. However, I am still unclear of the best practice for establishing a workspace for the reviewer table. During the training, I was under the impression that I needed to have the reviewer workspace in an SDE in before all team members could access/edit the reviewer table simultaneously. During our trials, we stored the reviewer table in a file GDB and my colleague and I were both able to make edits to records in the reviewer table (update correction status, Verification status, etc). We were also able to edit over eachother's records previous edits.
I have a few questions now:
1) Can I use a file gdb instead of an SDE or are there complications I am not seeing?
2) Should I expect to see a limit on the number of people able to access the file gdb? For example, it worked with 2 people but will it work for all team members (7)
3) We have a production SDE in which all of our features are stored. Is it possible to store the reviewer table in there as well? Or will that result in complications?
Any help would be great. And of course if you can recommend some references or sources that would be great too!
I have spoken with our database admin and he suggested the use of an SDE since it is in line with our standards.
Good idea. If you plan to have multiple users accessing and updating records in the Reviewer workspace, go with an enterprise Reviewer workspace. Even though you had two users accessing the file geodatabase, there could have been some data loss in the Reviewer Workspace. It is not recommended to have multiple people updating records in a Reviewer workspace that is in a file geodatabase. It's okay if multiple people are viewing the records in a Reviewer workspace that is in a file geodatabase.