Skip to end of metadata
Go to start of metadata

Overview

The purpose of this page is to collect information about enhancements, customizations or bug fixes that have been implemented locally, and have not been contributed back to the main foundation code base.  Implementers can check this page to see if others have built or are planning to build an enhancement similar to one they are also considering, and possibly share code or other resources.

Award / Award Budget

Indiana University

Contact(s): Victor J Kinzer

Award Hierarchy Award ID Naming Restructure


Summary: We modified the way that the system assigns Award IDs so that at the end of the currently formatted award Id (example: 102334-00001) a letter has been added.  This letter represents the number of levels down the hierarchy the node is located.  So the parent node will always end in an A (example 102334-00001A) all children of the parent node will end in a B (example 102334-00002B) and so on and so forth.  This was done because the numbering in the system currently happens based on the order the nodes are created, not where they appear in the hierarchy, so when award nodes appear in Medusa or in reports there is very little information about their relationship to the hierarchy structure overall.  The letters have been very useful to us for constructing our reports because each level of our hierarchy represents something very specific in our business process.

Technical Changes: The code that auto generates the Award ID's had to be changed.  No table changes were made as the Award ID already had a non numeric format (000000-00000)

Foundation Contribution: We are hoping to parametrize this enhancement and contribute it to the foundation.

 

Indiana University

Contact(s): Victor J Kinzer

Award Notice Delivery System


Summary: We setup a KC notification that can be manually triggered by a user from the Award Print interface.  The button sends a notification to all investigators and unit administrators who are signed up to receive these notices with a link to the Award notice output.  That link allows them to directly download the award notice (after authenticating into KC).  It stores the checkboxes that were selected at the time the notification was sent.  This allows us to distribute award notices without requiring staff to get into the Award and navigate it's UI directly.

Technical Changes: This includes SQL for the notification and Action trigger, as well as java to handle saving the award notice output settings at the time the award notice is sent, and to add the send UI element.

Foundation Contribution: This has been voted for inclusion by the foundation.  It will be included in a 6.X release.  The code is attached to KRAFDBCK-10952 - Data cannot be retrieved due to an unexpected error for any schools that want to pull the code down and use it in 5.X implementation.  IU developed this code using 4.0 initially, and then ported it to 5.1 so it should work in any 5.X implementation.

 

Indiana University

Contact(s): Victor J Kinzer

Award and Time and Money Transaction Type Separation

Summary: We setup a parameter to define which Transaction Types should be displayed in the Award Document.  We did this because there are certain transaction types that because of our business process we don't want to be used on Award Documents.  We treat our award nodes as a stable representation of a single funding event (a new piece of funding, a renewal, etc).  So when there is a No Cost Extension, rebudget, etc. we don't want the transaction type changed on our award nodes.  However, we do want those transactions saved in our time and money history.  This division was causing some confusion with our staff, so we setup this parameter so we could only display the transaction types that are valid for award nodes in the award, but list all transaction types in Time and Money.

Technical Changes: We created the parameter "AwardTransactionTypeAllowedValues" that will take the transaction type codes that are allowed to display in Award.  Then application code changes were made to check this parameter when populating the drop down list for Transaction Type in the award document.

Foundation Contribution: We are hoping to contribute this functionality to the foundation.

 

Indiana University

Contact(s): Victor J Kinzer

Award Search Returns saved Awards


Summary: We modified the award search screen so it could return saved award documents.  It does not return them by default though.  We added a radio button search parameter titled "Document Status" with three radio options "Final" "Saved" and "Both".  When Final is selected only the most recent final document is returned (current foundation functionality) when saved is returned only non finalized award documents are returned, and when both is selected the most recent final documents and saved documents are returned by the search engine.  This allows the user to more carefully search for what they're looking for, and to go directly into any pending versions of an award instead of having to go into the final version and press edit.

Technical Changes: The following files had to be updated for this enhancement: Award.java, Award.xml, AwardDocumentStatusConstants.java, AwardDocumentStatusValuesFinder.java and AwardLookupDaoOjb.java.  These files are all attached here.

Foundation Contribution: We built the search functionality to default to foundation behavior and to be entirely optional for the user and we are hoping to contribute to the foundation.

Conflict of Interest

 

IACUC

 

Institutional Proposal & Proposal Log

Indiana University

Contact(s): Victor J Kinzer

Add Subaward Panel to IP

Summary: We added the subaward panel from Award to IP.  This was done so that units could detail the subawards on their proposals when they were not doing a full budget document during routing.  The code that feeds data into Award, was modified so this data would be included in IPs when they are linked to Awards.

Technical Changes: The Subaward database columns were added to the Institutional Proposal records, and the UI elements were added to the IP document.  The code that feeds Award was also updated.

Foundation Contribution: We hope to parameterize and contribute this enhancement back to the foundation.


Indiana University

Contact(s): Victor J Kinzer

Institutional Proposal Cost Share Unit Listing

Summary: We added a unit lookup field to all cost share entries on all the budget modules.  This data pulls in from proposal development  Our business process requires all units who are providing cost share to approve the proposal development document, and as we don't always have a fiscal account setup at the time of proposal submission (example: New Faculty member's startup account, and we are submitting the proposal before their official start date) we needed a solid piece of data to direct this routing.

Technical Changes: Required an additional database column and modifications to the IP document.

Foundation Contribution: We hope to parameterize and contribute this enhancement back to the foundation.


IRB

Indiana University

Contact(s): Geoff McGregor

Human Subjects Participant Types - Required Attachments

Summary: If a Protocol includes certain participant types, require that a particular attachment type is included upon submission.  For example, if Children are included, require that a Request Form is attached.  

Technical ChangesRequired one new database table and changes to java and properties files.

Foundation Contribution Status:  None planned at this time.

 

Indiana University 

Contact(s):  Sara Benken

Amendments to Exempt Protocols 

Summary: IU needed the ability to submit/process amendments to exempt studies without using the current work around (processing them as expedited amendments). The changes are also merged back into the base protocol.

Foundation Contribution Status: Hope to contribute this code back to the foundation as soon as possible.

JIRA filed on 5/5/2014: KRAFDBCK-11144 


Indiana University

Contact(s): Victor J Kinzer

IRB Organization Correspondent Applicable Type Parameter

Summary:  We added the parameter PROTOCOL_ORGANIZATION_CORRESPONDENT_ORG_TYPES that is a comma deliminated list of the organization types which will invoke the permissions of the organization correspondent derived role.  OOB this role only assigns permissions to individuals who are associated with the Performing Organizations.  It was desirable for IU to provide permissions to individuals associated with Performance Sites as well.  Given that the organization types can be altered via maintenance table it seemed appropriate for this to be modifiable via parameter.

Technical Changes: A parameter was added to the system via maintenance document and the code that checks the Organization Correspondent permission was altered to account for the values in the parameter.

Foundation Contribution Status: We hope to contribute this code back to the foundation.

KRAFDBCK-10729 - Data cannot be retrieved due to an unexpected error

 

Indiana University

Contact(s): Geoff McGregor

IRB Non-employee view masked

Summary:  IU users which are not employees but given special "sponsored account relationship" or "non-employee affiliate" status have a masked access, where items such as protocol title can be hidden.

Came up in discussion of: https://jira.kuali.org/browse/KCENHANC-191

Foundation Contribution Status:  Hope to contribute this code back to the foundation as soon as possible.

JIRA filed on 5/5/2014:   KRAFDBCK-10692 - Data cannot be retrieved due to an unexpected error


Indiana University

Contact(s): Geoff McGregor

IRB FYI-Notify Enhancement

Summary: Problem: IRB was not always easily able to keep track of all notify IRB actions, because admin only needs to aknowledge, this does not support a process where IRB admins often need to go back and forth with PI/Dept Admin to get needed documentation. 
IU Solution: modeled a special routing for the FYI/ Notify IRB process to be similar to the amendment protocol process, except does not allow modification of the protocol itself other than notes and attachments. IRB can now obtain more information and even approve/disapprove action. Upon approve the attachments role into the notes and attachments history for tracking.

Foundation Contribution Status:  Hope to contribute this code back to the foundation as soon as possible.

JIRA filed on 5/5/2014:   KRAFDBCK-10691 - Data cannot be retrieved due to an unexpected error

 

University of Arizona

Contact(s): Kari Robertson

Added sortable column referencing Committee Name to All My Reviews

Summary:  We have Chairs/Reviewers who belong to multiple committees.  Based on the committee, responsibilities differ and there was no easy way to determine which committee was responsible for the pending Online Review.  To remedy this confusion, we added a column to the All My Reviews screen allowing the reviewer to see which Committee was assigned to the Online Review.

Technical Changes: Added committee name as an attribute and made it available for the protocol online review.

Foundation Contribution Status: We hope to contribute this code back to the foundation after we upgrade.

KRAFDBCK-10727 - Data cannot be retrieved due to an unexpected error


University of Arizona

Contact(s): Kari Robertson

HSPP workload search

Summary:  HSPP operates with a pool of associates who rotate responsibilities and are not assigned a set portfolio.  Given this structure, the action list does not provide detailed enough information for the HSPP associates about their workload.  We generated a new search HSPP (Admin Use) that combines protocol search, protocol submission search and a few custom data fields (associate name and tracking comments).  We have several saved search 'portals' that support the most frequent associate search functions needed.  This enhancement allows HSPP to easily locate all of their pending work.

Technical Changes: Significant but isolated. This included the ability for users to select multiple values from a listbox which required adjustments to Rice.

Foundation Contribution Status: We hope to contribute this code back to the foundation after we upgrade.

KRAFDBCK-10728 - Data cannot be retrieved due to an unexpected error

 

University of Arizona

Contact(s): Kari Robertson

Multiple pending Amendments/Renewals editing the same panels

Summary:  When creating an Amendment or Renewal w/ Amendment, the user must select which check boxes will be edited.  Only those panels (associated with the selected check boxes) can be edited.  While one Amendment/Renewal is pending, no other Amendment/Renewal can edit those areas already open for edit by another Amendment/Renewal.  Our implementation requires every Amendment/Renewal to update the areas associated with the Attachments and Others check boxes.  We have adjusted the code to always allow Attachments and Others check boxes to be selected (regardless of any pending Amendment/Renewal).  

Technical Changes: Added unique VERSIONING_ID column to disambiguate protocol attachments added to amendments/renewals from the base protocol.

Foundation Contribution Status: We hope to contribute this code back to the foundation after we upgrade if other schools are interested.

KRAFDBCK-10726 - Data cannot be retrieved due to an unexpected error

 

University of Arizona

Contact(s): Kari Robertson

Changed default Approval Date to reference date Chair selected <Approve Review>

Summary:  Currently the Approval Date (displayed when completing expedited, exempt, etc. approvals) defaults with the meeting schedule date. We have changed the default to be the date the Chair actually selected <Approve Review>. Given our business process, this more accurately reflects the date of the Approval and Expiration (Approval +364).

Technical Changes:  Modified ActionHelper.java

Foundation Contribution Status: We hope to contribute this code back to the foundation after we upgrade if other schools are interested.

KRAFDBCK-10725 - Data cannot be retrieved due to an unexpected error

 

University of Arizona

Contact(s): Kari Robertson

Edit Risk Levels through administrative correction

Summary:  We have added the ability to edit the risk levels for the main protocol (not amendment/renewal) within an administrative correction.

Technical Changes: Code only

Foundation Contribution Status: We hope to contribute this code back to the foundation after we upgrade.

KCENHANC-183 - Data cannot be retrieved due to an unexpected error

 

University of Arizona

Contact(s): Kari Robertson

Reference to Amendment/Renewal last modifying the attachment

Summary:  We have added a reference (A00X/R00X) to the attachment header bar displaying which Amendment/Renewal last modified/added each attachment.  Also added ability to filter by Amendment/Renewal number on attachments tab.

Technical Changes: Code only

Foundation Contribution Status: We hope to contribute this code back to the foundation after we upgrade.

KRAFDBCK-10724 - Data cannot be retrieved due to an unexpected error

 

 

Negotiations

 

Indiana University

Contact(s): Victor J Kinzer

Add Activities and Attachment Numbering to the Activities Subaward titles

Summary: We modified the subpanels in the activities section to display a number that indicated how many items are in the subpanel.  So the activities subpanel will indicate how many activities there are, and the All Attachments subpanel will indicate how many attachments are included in total in the negotiation.  This is consistent with behavior in other modules.  So this was a matter of getting the Negotiation module to the same level of functionality displayed in the other KC modules.

Technical Changes: The required a Java change, but no data changes were made to the application.  The code is attached here.

Foundation Contribution: We hope to contribute this enhancement back to the foundation.

 

 

West Virginia University

Contact(s): David Dufalla

IRB Admin Action List

Summary: WVU created a special IRB actions search that allows user to manage the status of protocols submitted to administrators.

User selects the protocol type and the submission status to view those action items by category. Each item appears in the search also showing who (based on initials) the protocol has been assigned to.  These views can also be downloaded to excel file.

After the review status is marked as completed, the protocol is removed from the action list.

Foundation Contribution Status:  Hope to contribute this code back to the foundation as soon as possible.

JIRA filed on 5/5/2014:   KRAFDBCK-10690 - Data cannot be retrieved due to an unexpected error

 

 

Proposal & Budget Development

Indiana University

Contact(s): Victor J Kinzer

Proposal Development Credit Split Default Distribution Button

Summary: On the credit split section of the Key Personnel page we have put a default distribution button.  This button assigned 100% credit to the PI, and then it assigns 100% unit credit to the Lead Unit on all personnel.  This was done because only a few schools at our institution track credit split beyond this level of complexity.  For the majority of units it is not used, and this saves a significant amount of time aggregated across our institutions proposal activity.  The button only populates the fields in credit split the moment it is pressed.  The data can be modified after the fact, and any user can still choose to enter a more complex credit split breakdown.

Technical Changes: No database, or field changes had to be made.  A piece of code that manipulates the UI fields when the button is pressed had to be added.

Foundation Contribution Status: We hope to parameterize and contribute this enhancement back to the foundation.

 

Indiana University

Contact(s): Victor J Kinzer

Proposal Budget Cost Share Unit Listing

Summary: We added a unit lookup field to all cost share entries on all the budget modules.  In Proposal Development this information informs routing.  Our business process requires all units who are providing cost share to approve the proposal development document, and as we don't always have a fiscal account setup at the time of proposal submission (example: New Faculty member's startup account, and we are submitting the proposal before their official start date) we needed a solid piece of data to direct this routing.

Technical Changes: Required an additional database column and modifications to the default Proposal Development routing code.

Foundation Contribution: We hope to parameterize and contribute this enhancement back to the foundation.

Indiana University

Contact(s): Victor J Kinzer

Add Subaward Panel to Proposal Development

Summary: We added the subaward panel from Award to Proposal Development.  This was done so that units could detail the subawards on their proposals when they were not doing a full budget document during routing.  The code that feeds data into IP, was modified so this data would be included in IPs when they are created.

Technical Changes: The Subaward database columns were added to the Proposal Development records, and the UI elements were added to the Prop Dev document.  The code that feeds IP was also updated.

Foundation Contribution: We hope to parameterize and contribute this enhancement back to the foundation.

Indiana University

Contact(s): Victor J Kinzer

Add Revision Type Drop Down Field

Summary: We added an additional dropdown field to proposal development called Revision Type.  We created a maintenance document that would populate this field with various actions that are associated with the revision proposal type.  This allowed us to stay within the grants.gov proposal type structure while capturing additional data we needed for reporting and business process purposes.  As revisions include both monetary and non monetary actions (supplements being the monetary action) we needed to be able to differentiate between those actions for our institutional reports.

Technical Changes: A new maintenance document was added to the system (ProposalRevisionType) and an associated table was added to the database to hold the revision types.  The Java code was also updated to account for this new maintenance table, and proposal development document data.

Foundation Contribution: We hope to parameterize and contribute this enhancement back to the foundation.

University of Arizona

Contact(s): Jessica Peck

Budget Modification for non-12 month appointments

Summary:  Helps budget academic, summer, basically any none 12 month appointments. The current behavior in FND is it defaults in the line item start/end date with the Project start/end date.  But if you're attempting to budget a 9 or 3 month individual the user would have to know they need to manually edit these fields with a 9 or 3 month period. UA's fix is that if it's a 9 month or 3 month appt the system automatically brings in the appropriate dates.

Technical Changes: see KRAFDBCK-10542

Foundation Contribution: see KRAFDBCK-10542

University of Arizona

Contact(s): Jessica Peck

Proposal Workflow Dashboard

Summary:  There is no easy way for SPS/campus to search for enroute proposals.  UA created a custom search/dashboard link from Research/Unit/Central tabs that allows users to search for enroute proposals by a number of attributes:

  • Workflow Stop (i.e. PI, Department, College)
  • Route Stop Department/College
  • Route Stop Date From/To
  • Proposal Number
  • Document Number
  • Proposal Title
  • Sponsor Name
  • Sponsor Deadline Date From/To
  • Proposal Person Full Name
  • Lead Unit
  • Lead College

Also, this dashboard gives SPS staff edit rights (new permissions created) for additional columns in the search results to assign and SPS Reviewer and mark whether it's gotten expedited approval to jump to the top of the list.  This information displays for other users in the search results so they can see who is assigned to work on their proposal and for the OSP stop what order they are in the queue.

Technical Changes: code and database

Foundation Contribution: We hope to contribute this code back to the foundation eventually

 

Report Tracking

 

Subawards

 

Shared / Global

Indiana University

Contact(s): Victor J Kinzer

Add the Ability to Create an Addressbook Entry to the Addressbook Lookup Screen

Summary: We added text to the Addressbook Lookup screen that comes up when you do an Addresbook search from within a module with a link to create a new rolodex entry.  When you click on the link it opens a new rolodex document in a new browser tab.  This allows a user to add a new rolodex entry that is needed when they discover they need it in the middle of doing a document.  (Note this has been identified as a FE need by the preaward committee).  We provided rolodex creation rights to our entire user community.  

Technical Changes: Java changes were made that cause the link to populate after an addressbook search is completed.  We did some permission enhancements to give the user community creation rights with no delete or edit rights to the rolodex table.

Foundation Contribution: A modified version of this code has been built into 5.2.1

Indiana University

Contact(s): Victor J Kinzer

Create a Yes/No Custom Data Type

Summary: We added a boolean custom data type that renders in the application as a set of O Yes O No radio buttons.  This allows us to avoid the ArgValueLookup workaround.  It creates a much more user friendly interface.  We opted for radio buttons instead of a checkbox because we needed to be able to set the field as "required" so null had to be an option.  With a checkbox the interface would always be in a valid state, either yes or no.  With radio buttons it was possible for the field to have a null state, so it was possible to validate that the staff member had actually updated the field.

Technical Changes: A new custom data type of "boolean" had to be added.  Java code was included in the system to save a "Y" in the database table if Yes radio button was selected, a "N" was saved to the database if the No radiobutton was selected, and if no radio button was selected the field was left "null".  This allowed us to move directly over from our previous argvaluelookup field types in the maintenance tables without doing any data conversion for our existing yes no custom data fields. (Code Change to customData.tag on lines 135-141) (SQL to add custom data type to the maintenenace tables)

Foundation Contribution: This has been contributed to the foundation, and is being voted on by the technical subcommittee.

 

Indiana University

Contact(s): Victor J Kinzer

Direct Link to the Rule Lookup in the KC Portal

Summary: We added a direct link to the Rule lookup from our KC portal.  This was needed because the functional administrators needed to be able to lookup Rule IDs when designing questionnaires and working on KRMS analysis.

Technical Changes: We had to provide a link directly to the KRMS rules lookup in our KC portal.  This rule lookup already has KRAD based XML setup, but it's only linked from within the Agenda document.  We just provided an addiional access point that didn't require entering an agenda document.

Foundation Contribution: We are hoping to contribute this to the foundation.

Partner Contributions

KC Contributed Code Process

key summary reporter priority status resolution fixversions versions contributing institution

com.atlassian.sal.api.net.ResponseException: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

View these issues in JIRA

 


 

  • No labels