Skip to end of metadata
Go to start of metadata
  1. Ensure gForge has an entry in the "ballot" and "specification" fields for the specification.  If not, have the gForge manager add them.
  2. Download the spreadsheets for the ballot
  3. Check each spreadsheet to verify that appropriate contact information including email is filled in on the heading page and that the spreadsheet was actually submitted to the right ballot.  (If not, talk to Lynn about whether it's possible to transfer the spreadsheet to the correct ballot - i.e. if the commenter was a balloter on both specifications)
  4. Run the amagamation macro to combine all of the spreadsheets together
  5. Look through the ballot summary spreadsheet for any comments that say more than just "see comments submitted by" or "see spreadsheet" - i.e. where someone has made a ballot comment outside the spreadsheet - and add those comments to the amalgamated spreadsheet
  6. Ensure the first row is the row that says "Comment Number" (you'll probably need to delete the top line).  Also make sure there are no blank lines in between ballot lines
  7. Check that the column headings in the first row don't have any carriage returns in them (usually an issue for Column Number and Disposition Comment columns)
  8. Ensure the "Ballot" column is filled with the appropriate value from the gForge "Specification" drop-down (not the "Ballot" column)
  9. If spreadsheet line has a tracker #, the only elements that need to be present are the Ballot, Vote and Type and the pink balloter columns.  If other information is specified, check to make sure it aligns with the information in gForge and, if so, delete it from the spreadsheet.  If not, add any "additional" information from the spreadsheet as a comment to the gForge issue and then remove the extra fields from the spreadsheet.
  10. Do a scan of the Resource(s), section, HTML page name(s) and URL columns and find places where people put content in the wrong place and fix it
    1. Resource(s) can only be a comma-separated list of resource names as found in the gForge Resource column.  (The full string in gForge must be used).  Check the names are an exact match for what's in gForge (including old names in brackets where necessary)
    2. HTML Page name(s) can only be a comma-separated list of page names as found in the gForge Page column.  (The fully string in gForge must be used).  For IGs, the page will most commonly be "(profiles)" because we don't have profile-specific pages, though index, toc and a few others may still be relevant.
    3. The URL must be a single URL (not multiples) and must start with http://hl7.org/fhir or http://build.fhir.org or other official ballot site for specification content
    4. The Section can be anything, but should be section numbers or names.
    5. If necessary, move content that was placed in one of those four columns that can't properly live there into the "Ballot Comments" column
  11. Ensure the Chapter, Page #, Line #, Artifact ID columns are empty.  If necessary, move content that was placed in one of those columns the "Ballot Comments" column
  12. Ensure that all lines that don't have a tracker # have content in at least one of the Resource(s) and HTML Page name(s) columns.  If this content isn't present, look at the comment and figure out what page(s) and/or resource(s) apply and fill the columns in.  For IGs, we don't actually list IG pages, so most commonly you'll just have an entry in HTML Page name(s) that says "(profiles)".  In some cases, the comment may be about numerous artifacts or won't apply to any pages at all, in which case "(many) or "(NA)" are appropriate page values.
  13. If a tracker # is specified for a row, ensure that only the Ballot and Vote and Type as well as the submitter columns are filled in.  If other information is present, check that it jives with what's in the Tracker, and if so, wipe the unneeded information from the spreadsheet.  If not, figure out if gForge needs to be updated or if someone has corrected incorrect categorization in the ballot spreadsheet (and when done, wipe the unneeded informtaion from the spreadsheet)
  14. Ensure the Vote and Type column only contains valid vote values as per the dropdown in the Setup page (i.e. no-one overrode the dropdown formatting rules).  If appropriate, you can change items that are true typos to A-T (as they're automatically applied and found persuasive)
  15. Sub-category must be specified for A-S and NEG and should be omitted for everything else
  16. Every line must be given a summary.  The summary must be no more than ~100-150 characters and should be an appropriate summary to show in the summary line of the gForge item.  This will be the only thing you see in the gForge list, so every row should have a distinct summary (possible exception being typos)
  17. Check that the submitter and email columns are filled in for every single row (grab the information from the ballot summary or by contacting the balloter if necessary).  Also, check to see if the submitter and onBehalfOf already exists in the Real Submitter list and, if so, make sure their name is entered identically as in Real Submitter (whether in the submitter or On behalf of fields).  For everyone who's not in the list, send the names to the gForge manager and have those names added.  If a name is in both the submitter and on-behalf of column for a single issue, wipe the on-behalf-of.  If multiple names are listed as a submitter or on-behalf-of, pick only one (generally whoever's already in gForge).
  18. If the item is a duplicate, give it a Comment grouping of "_Duplicate" and in the Triage Note, indicate what it's a duplicate of in the "Proposed Disposition" column.  If the item is a confirmed typo, set the Comment grouping to "_Typo" and put a disposition of "Persuasive" and a Disposition Comment of "auto-approved"
  19. Ensure every line that isn't tied to an existing gForge issue is associated with a Disposition WG (Work Group) - again must match the precise name in the gForge drop-down.
  20. If you want (and have time before load), you can also fill out the Comment grouping for other elements (must be one of the Group drop-down values), Schedule (must be one of the Schedule drop-down values), Triage Note (gets added as a comment) Disposition and/or Disposition Comment columns (for preliminary disposition).  You can request additions to Group and Schedule if they'll have cross-WG utility
  21. Ensure that there are no "blank" rows with item numbers
  22. Provide a copy of the "cleaned" spreadsheet to the gForge load coordinator and resolve any issues they find during the load process (related to something missed during one of the above steps).
  • No labels