Enable a workflow for the priority meetings that uses a google sheet to lower the friction.

[mikeaintworkin]

I want to be able to run the priority team meeting out of a spreadsheet, using information reported by the query.

I've walked through this. So far what I need is:

• create a list of all labels from all of the issues in the data.
• Then add that list as columns to the end of the report.
• Then display that list and for each Issue/PR there should be a 1 in the column of any of the labels that it has. INclude the size labels.
• duplicate the Status column information. In the spreadsheet there will then be an original value and a new value. The new value will be the outcome of a change in column. The new value will be set after the planning meeting. call this OG Queue column
• Add a comments column. This will be used during the planning to add any comments . The contents will be added as a comment to this issue/pr after the planning meeting
• enable the data collection to receive as input the project name.
• write up a draft of the workflow that this is part of.

This is my first step towards making use of what I've done to improve one of our processes: the priority meeting. The work on this issue will cover the pre-meeting preparation (via the documenation) and the meeting itself (by making the columns line up and otherwise display the data in such a way as to make the meeting flow easier.

I'm working through the process using 2023_02_08 Sprint Calendar Planning tab

[mikeaintworkin]

This has lead me down the path of the key() function and xsl:key element and for-each group element.
It's too late on a friday to start this.
It is opening up my thinking though.
I may be able to move a lot of the processing into xslt and output an html page at the end.
e.g. Every time I run the command I get an updated html page.

[mikeaintworkin]

This has lead me down the path of the key() function and xsl:key element and for-each group element. It's too late on a friday to start this. It is opening up my thinking though. I may be able to move a lot of the processing into xslt and output an html page at the end. e.g. Every time I run the command I get an updated html page.

Opened a separate issue for this effort.

[mikeaintworkin]

It seems like the easiest way to do these steps is to use pandas in python.
I'm really rusty so the next step is to get through this part with a tutorial.
e.g.
https://realpython.com/pandas-dataframe/
https://www.geeksforgeeks.org/how-to-read-text-files-with-pandas/

created process_flat_file.py
notes are around p 163 in my notebook for 2/25

 Then add that list as columns to the end of the report.
 Then display that list and for each Issue/PR there should be a 1 in the column of any of the labels that it has. INclude the size labels.

[mikeaintworkin]

closing down for the night.
Just realized that I might be able to do this part easily in xslt.
Create a unique list of a lables and save this as a variable.
As I process each Issue/PR, just loop through the unique list looking for a match.
if there's a match add a 1 for that column.
Else add a 0.

It's a toss up if this is easier than python or not.
I'm curious if it is as easy as I'm thinking

https://stackoverflow.com/questions/2291567/how-to-use-xslt-to-create-distinct-values.
https://stackoverflow.com/questions/32775600/accessing-multiple-xml-files-via-xsl

https://gandhimukul.tripod.com/xslt/grouping.html

[mikeaintworkin]

Left off: Working on get_list_of_Labels.xsl

• I've created the xml snippet containing a unique list of (90!) labels from the data
• I've printed out a header row

The next step is to loop through each output line for the labels and print a 1 or 0 in the columns where the labels are present.

[mikeaintworkin]

It feels like a hack, but I was able to create the data I wanted using nested for loops in the xslt file.

'TEST'|Type|Status|IssueNumber|Title|LabelsCount|LabelString|AssignedSize|Repository|closingIssuesReferences|Size: 3|Feature: API|User Role: API User|NIH OTA: 1.7.1 (reArchitecture)|Size: 33|NIH OTA: 1.2.1|Size: 80|Deliverable: 5 Core PIDs|QDR|Feature: Metadata|Type: Bug|Feature: Style Guide|User Role: Superuser|Feature: Controlled Vocabulary|Hackathon: JSF|Size: SprintTail|Feature: External Tool|Feature: User Guide|JHU|Size: 10|DANS|NIH OTA: 1.4.1|User Role: Sysadmin|Feature: File Upload & Handling|Feature: Code Infrastructure|Feature: Installation Guide|Containers & Cloud|Tech Debt|Type: Feature|Sprint Retrospective|DataverseNO|Feature: Account & User Info|NIH: NetCDF|Working Group: SWC|HERMES|NIH OTA: 1.3.1|Feature: Developer Guide|Feature: Indexing|Feature: Harvesting|Testing: API|pm.Sonia|UI/UX: Design|Payara 6 Upgrade|ASU|epic.8701|NIH OTA DC|pm.epic.nih_harvesting|Feature: Search/Browse|Type: Suggestion|User Role: Hackathon Participant|NIH OTA: 1.5.1|Feature: Request Access Workflow|Feature: API Guide|Size: NoSprintCost|bk2211|ops: User Accounts|Support|Support: prod. data corruption|postmortem|bklog: Deliverable|bklog: NeedsDiscussion|Feature: Installer|bklog: Collection|Size: Queued|NIH OTA: 1.1.1|Feature: Admin Guide|Feature: Geospatial|bug|enhancement|Status: UX & UI|Feature: Publishing & Versions|Feature: DOI & Handle|hdc|3a|Feature: Terms & Licensing|Feature: Accessibility|pm.epic.nih_harvesting_framework|Feature: Permissions|Feature: Metrics + Reports|Hackathon: More APIs|User Role: Curator|User Role: Depositor|Feature: Performance & Stability|Size: 130|dependencies|DevOps: Problem|GDC: Interop With DV|sz.Small|spike|Dataset: large number of files|
'TEST'|'PULL_REQUEST'|'Clear of the Backlog'|9193|'IQSS/9189-fix non-Globus properties'|1|'Size: 3'|3|'dataverse'|'9189'|1||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
'TEST'|'ISSUE'|'Clear of the Backlog'|208|'Add Binder button for operating on datasets with Jupyter notebooks, Python, R, etc.'|1|'Size: 3'|3|'dataverse.harvard.edu'||1||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
'TEST'|'PULL_REQUEST'|'Clear of the Backlog'|8827|'7000 mpconfig files basic'|6|'Feature: File Upload & Handling','Feature: Code Infrastructure','Feature: Installation Guide','User Role: Sysadmin','Containers & Cloud','Size: 3'|3|'dataverse'||1||||||||||||||||||||||1|1|1|1|1||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||