3DB Revision History
Click the ⊞ to see details - --- v1.5 February 2021 - Present ---
- Common Functions Expanded:
- Common functions have been created for database connection and querying.
- Common functions have been created for session creation, validation, updating
and ending.
- Common functions have been created for user authentication. Full login is still
being developed.
- Some more html generation functions have been added as well.
- Documentation can be found here and will be updated as functions are added.
- Prev and Next Buttons:
- Viewing pages for Defeats and Disables have "Prev" and "Next" buttons.
- "Prev" button takes user to previous Defeat or Disable with the same status.
- "Next" button takes user to Next Defeat or Disable with the same status.
- For "Removed" Defeats or Disables order is determined by Removal date.
- For all other status types, order is determined by YYYY-## id.
- Better Messages:
- All error and information messages were given the same styling.
- Positions of several messages changed to prevent hiding of page elements.
- Some information messages were added to confirm successful operation.
- Misc. Bug Fixes:
- Fixed bug that was generating incorrect implementation/removal times.
- Fixed bug that caused query failure when a comment was entered with a ' in it.
- Fixed a couple of cross-browser styling issues that caused certain parts of the
user interface to be drawn differently between Firefox and Chrome.
- --- v1.4 August 2020 - February 2021 ---
- Shared Login:
- Initial code has been added to allow for session sharing with other ISAC apps.
- Only a single login will be needed to gain access to all compatable ISAC apps.
- Common Functions:
- Steps are being taken to allow other ISAC apps to use the same functions to generate html.
- This will allow a common look and feel for all ISAC apps and simplify support and development.
- HTML generation of the page header, footer and side buttons. Database access and login
functionality are also included
- More to come in the future
- Session Management Cleanup:
- Some general streamlining of how new sessions are created and validated.
- Email Notification Refinement:
- Email notifications can be turned on or off for a particular system.
- Accessed through the "Add/Modify System" button.
- When unchecked, email notifications are not sent out for Defeats or Disables
associated with that system.
- Acknowledgement Requirements Changed:
- Acknowledgements are not required for Defeats or Disables that were removed more than
6 months ago.
- This brings 3DB acknowledgements into compliance with TSN 1.5.
- --- v1.3 March 2020 - August 2020 ---
- Email Notifications:
- Emails are sent out when a new Defeat or Disable is submitted as "Active" or "Removed".
- Emails go out for existing Defeats and Disables if the status is changed to "Active"
from any other status or if the status is changed to "Removed" from "Active" only.
- Emails only go to users associated with the selected complex.
- Acknowledgments Refined:
- Acknowledgement is no longer required if a Defeat or Disable is removed
before you have acknowledged implementation.
- Auto-acknowledgement is not done if a valid acknowledgement already exists for the user. This was filling
up the acknowledgement table unnecessarily fast
- Acc. Complex Integration:
- Filtering on Accelerator Complex added to various drop-down lists to only give options appropriate
to the selected Accelerator Complex.
- Each user now has an Accelerator Complex assigned to them. This can be modified on the "Add/Modify User" page.
- Each system now has an Accelerator Complex assigned to it. This can be modified on the "Add/Modify System" page.
- A user or system can be assigned or moved to a particular complex or to "All".
- --- v1.2 June 2019 - March 2020 ---
- User Acknowledgement:
- Checkboxes are provided for users to indicate that they have read
and understood the Defeat or Disable in question.
- An acknowledgement is required when a Defeat or Disable is Activated and
when it is Removed.
- This replaces emails sent by the system to inform users of new Defeats
and Disables.
- Users can choose to add or remove their acknowledgement at any time.
- Acknowledgement is auto-checked for a user that edits an Active or Removed
Defeat or Disable.
- Administrators have the ability to remove all acknowledgements for a given
Defeat or Disable.
- A marker is shown in the search results list for Defeats and Disables
indicating ones that require acknowledgement.
- The person adding or removing acknowledgement(s) as well as the time is archived.
- Add/Modify System Page Added:
- Administrators now have the ability to add a new system or modify an existing system.
- The system name must be unique.
- Accelerator Complex Added:
- Groundwork has been laid out to facilitate use of the DDDB by other control rooms.
- Control rooms are differentiated by "accelerator complex".
- Additional Consultation Added:
- A second "In Consultation With" drop-down has been added to the Defeat and
Disable forms.
- Both drop-downs are optional and either or both can be selected.
- Tag Location Separated:
- Details regarding the location of tags associated with Defeats and Disables has been
moved to a separate field.
- This field is required for submission of form.
- Misc:
- The column widths in the search results tables have been adjusted to prevent wrapping
of text when undesired.
- Useful information pop-ups have been added to several columns on search results page.
These are displayed when the mouse is held over them.
- When a new Defeat or Disable is created, a status of Active is selected by default.
The user can select a different status if desired.
- The option of having 0 tags for a Defeat or Disable was removed. The minimum is 1 tag.
- Added pop-out search buttons to LHS button list.
- Made change details on history page collapsable.
- Sept. 2019 Bugfix:
- Fixed bug that prevented adding a comment to a Defeat or Disable.
- Fixed a bug that caused Cancelled Defeats and Disables to indicate that they needed
acknowledgement.
- Non-UTF-8 formatted text would sometimes cause SQL errors upon submission. All forms now
display and submit explicitly in UTF-8 to match the database formatting.
- --- v1.0 November 2018 - June 2019 ---
- Initial Version of DDDB:
- This is the initial release of the DDDB.
- A relational database is used to store information related to interlock defeats
and device disables.
- A web interface is used to add and/or update information in the database.
- Access to features that write to the database is controlled by TRIDENT authentication.
- Use of the application is restricted to systems under the purview of the ISAC control room.
