view evs_history in Protégé

[bdionne]

The ability to view a concept’s history from within Protégé would keep me from having to use a separate webapp to view this information.

[NCIEVS]

• this is the equivalent of evs_history
• current options to record this history are a) write to file , b) write to DB, c) both
• we will need to create a plugin to read the history from within protege

[NCIEVS]

To add another clarification, the web app that this would replace is used to view evs_history dating back to when we first started collecting history (2003-2004).

The web app is accessible inside the NIH network, accessible from http://ncias-q1319.nci.nih.gov:18080/QueryHistory/.

[bdionne]

History needs to be configured, similar to report writer. User can specify:

• start and end dates of history
• unique
• user
• operation

Not specifying anything means to retrieve all the history

[singhik]

@bdionne : Hi Bob, The 'Start Date' and 'End Date' buttons under 'EVS History' appear shaking/vibrating when trying to select a Date , not sure if this is OS specific ... I can do a screen share and show as it is not possible to put that as a screen print

[singhik]

@bdionne @NCIEVS :: Hi ,

1. When EVS History search results are Exported as .xls File, the Values do get Exported correctly but the 'Column Name' does not get Exported , i.e. 'Date', 'User Name' ,'Code', 'Name', 'Operation' and 'Reference' , is this Expected ? please refer below screen print ::

2. When EVS History Search results are Exported as csv file , all the values get merged in one cell , is this Expected ? please refer below screen print ::

[bdionne]

correct, what gets exported are the history records. This file is exactly equal to what's persisted on the server. We could add columns headings, but currently there is no requirement for that.

Note that the records are tab delimited. I don't use eXcel but I imagine this can be imported into separate cells by specifying tabs?

I was also considering adding a JSON endpoint for use as a command line utility together with JQ (@NCIEVS - something for admin types?)

[singhik]

@NCIEVS @bdionne :: Hi , QA has validated below Functionality for EVS History Tab, please provide your inputs if this coverage is sufficient for closure ::

'EVS History' search results display using 'UserName', 'StartDate','EndDate' and 'Operation=ALL' and validation of Search results .

'EVS History' search results display using 'UserName', 'StartDate','EndDate' and 'Operation=SPLIT/CREATE/MODIFY/RETIRE/MERGE ' and validation of Search results .

'EVS History' search results display using 'UserName', 'StartDate','EndDate','Code' and 'Operation=ALL' and validation of Search results .

'EVS History' Search Results Export validation when Exported into .Excel and .Txt format .

'EVS History' Search Results validation using only 'UserName' and 'Operation' .

'EVS History' Search Results validation using only 'StartDate',"EndDate' and 'Operation' .

'EVS History' Search Results validation using only 'Code' and 'Operation' .

Attached are the screen print results for reference :: Issue 64.docx

[bdionne]

that seems like you got all the cases

[NCIEVS]

@bdionne, let's chat about the json endpoint. That would be separately from this ticket though, so this ticket could be closed if it passed QA.

[singhik]

Closing this ticket as verified by QA , JSON endpoint addition will be decided by Gilberto and Bob and will be scoped for future Milestone as applicable ...