How do I use the RSA-911 Edit Checker?
Go to the web page and click on download link.
What RSA-911 Edit Specification is being used?
The tool incorporates the latest rules and data validation items. To find the version being used in your software, go to Options –> About and a dialog box will display with your current RSA-911 Edit Specification version number. (see screenshots below)
What RSA-911 Policy Directive is being used?
We generate the rules from the RSA-911 Edit Specification. There could be a RSA-911 Directive change that has not yet been reflected in the RSA-911 Edit Specification. The rules will be updated as the RSA publishes an update to the RSA-911 Edit Specification.
What technical skills are needed to run the tool?
The tool is intended to be run by anyone with access to RSA-911 extract file. Resolving the errors would require a professional with general knowledge of the VR industry.
How do I report an issue?
Email us at RSA911support@RSA911editchecker.com
Or if you have a GitHub account, follow these steps to post an issue, which could be a question, an error that you noticed or an idea for a future enhancement.
- Go to the RSA-911 Edit Checker repository
- Click “New Issue” (green button)
- Type issue into the field
- Submit New Issue (green button)
- Congrats! Your issue is now shared with the community
- You’ll receive a notification email that your issue is shared with the community and see all future comments related to the issue.
How do I modify a rule?
Agencies can modify rules and propose a change that would be accepted by the GitHub moderator. They can propose rules for inclusion into the Community Checks.
How do I add a rule?
Members of the open-source community can propose an additional rule in the GitHub community.
What technical skills are needed to add rules?
Each rule is defined by an XML file. The rule enforcement is accomplished with a SQL query contained within the XML file. To add a rule requires both XML and SQL knowledge. Contributors can reference existing XML and SQL examples with the 817 RSA-911 edit checks, as well as the community checks.
What’s a “reasonableness” check?
It’s a check that identifies outlier data and finds obvious errors, such as a wage that’s over $1,500,000 a year or a participant that’s younger than 12-years old. These checks are intended to improve the integrity of the data and are separate from and not enforced by RSA. These checks can be added or maintained as agency-specific checks, or proposed for community check submission.
What’s a community check?
If an agency believes that a reasonableness check can be used by other agencies it can be proposed to the open-source community. If the open-source community agrees then that reasonableness check is included in the community checks, available to all agencies.
How secure is the RSA-911 Edit Checker with respect to the data?
The RSA 911 Edit Checker tool runs locally on your machine and your data is never sent anywhere else. We have also incorporated the following security protections within the tool to help protect PII while on your desktop.
- RSA-911 Extract File – The RSA-911 Edit Checker does use the RSA-911 extract file to run the rules on. It will read the extract file into a SQL Express database, but uses a SQL temporary database table to do so. So, once the RSA-911 Edit Checker is closed, there is no RSA-911 extract information left in the database.
- When the RSA-911 Edit Checker does complete running its rule checks, there is an option to generate an error report. This error report is generated into an Excel file. If that Excel file is closed, without saving, there is no error report information left on the workstation. Only in the case of saving the error report is there any information saved on the workstation.
- For support, there is an option to export the RSA-911 extract file in the case it can be used to troubleshoot a rule check. When using this export option, the extract is exported without PII. Specifically, Element5, Element6 and Element8 are cleared. This cleansed, secured export file is opened in Excel and, if not saved, then there is no extract file information left on the workstation. Only in the case of saving the cleansed, secured export file is any information saved on the workstation but it is without PII.
Is there a workaround for the “SQL Express 2012 not installed” error messaging I’m getting?
Run as an administrator. Do note that the installation does need to occur using the user’s identity and running Internet Explorer as Administrator to provide the installation the enhanced security that it needs.
Please remove the RSA-911 Edit Checker, launch Internet Explorer with right-click so you can run as Administrator, and then run the installation from that Internet Explorer session. This will give you the temporary raised security you need to install SQL Express while also still installing as the user rather than the local administrator.
Is there a workaround for the “What is the EULA agreement” error I’m getting (IT won’t allow the user to push the download button without review first)?
Feel free to pass on the following EULA to the IT department:
This is free and unencumbered software released into the public domain.
Anyone is free to copy, modify, publish, use, compile, sell, or
distribute this software, either in source code form or as a compiled
binary, for any purpose, commercial or non-commercial, and by any
means.
In jurisdictions that recognize copyright laws, the author or authors
of this software dedicate any and all copyright interest in the
software to the public domain. We make this dedication for the benefit
of the public at large and to the detriment of our heirs and
successors. We intend this dedication to be an overt act of
relinquishment in perpetuity of all present and future rights to this
software under copyright law.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.
For more information, please refer to <https://unlicense.org>