|
|
| Line 7: |
Line 7: |
| | =Notes and action item= | | =Notes and action item= |
| | ===Updates=== | | ===Updates=== |
| − | '''PCO'''
| |
| − | *Thanks to the community for sharing your May promos with us
| |
| − | '''Stephane Bachard - New reporting requirements - Supply Chains Act reporting requirements'''
| |
| − | *This is a policy led initiative
| |
| − | *It’s a reaction to the Act we have to follow
| |
| − | *Departments have some flexibility where to post
| |
| − | *Formats are flexible
| |
| − | *Have to follow Official Languages Act
| |
| − | *Public Safety has to make their reports available in a central location
| |
| − | *Can be .pdf or web only, as long as it’s accessible
| |
| − | *Public Safety is working to post their report early as an example for other departments to follow
| |
| − | *Timeline: the questionnaire and .pdf version are due May 31, but as far as publishing on website, there are not definite deadlines
| |
| − | *For more information: https://www.publicsafety.gc.ca/cnt/cntrng-crm/frcd-lbr-cndn-spply-chns/index-en.aspx
| |
| − | '''Questions:'''
| |
| | | | |
| − | Q: Are you going to come back when Public Safety Publishes its reports?
| |
| − |
| |
| − | A: Yes, I can come back.
| |
| − |
| |
| − | Q: Do we need to alert other teams in our department about these reports?
| |
| − |
| |
| − | A: Other teams should be aware of this.
| |
| − |
| |
| − | '''Mary Beth Baker PCO, Stephane LeBlanc - VAC - BROKEN LINKS'''
| |
| − | *At VAC, we moved from Cold Fusion to Drupal
| |
| − | *Resulted in almost 7,000 broken links by day 2
| |
| − | *To fix the problem was a joint effort with IT and the Web team
| |
| − | *This brought up the issue - what is the “industry standard” for amount of broken links
| |
| − | *Some say 5%
| |
| − | *We put in a customized page to alert users that we were making some changes, with navigation help, but internally this page wasn’t popular
| |
| − | '''Q''': There’s an alert at the top of the page, is that how you told people to contact you? And maintenance implies a short time period.
| |
| − |
| |
| − | '''A:''' Yes, that’s what we used. At the beginning we got some contact, but it has greatly gone down over time.
| |
| − |
| |
| − | '''Comments from chat - managing broken links:'''
| |
| − | *We used to have Link Tiger for broken links, a very small investment for a solid tool. But now with Drupal we have a built-in broken link report.
| |
| − |
| |
| − | *The best part of SiteImprove is that you can send out automatic reports for both broken links and accessibility issues, this push style reporting is super useful as a reminder
| |
| − |
| |
| − | *At GAC, we monitor broken link CLICKS, not the actual broken links. If the broken links are not getting clicked, it's not really a problem. We try to address links that are clicked more than 10 times a week over many weeks. At 10 clicks/week we end up having to review / fix just a handful of links each week which is manageable by our busy teams
| |
| − | Also note that broken links can also be caused when redirects are left in place longer than they should be...redirects should only be used temporarily, until user traffic is going straight to the new URL. If Principal Publisher implemented your redirects in MWS, please let us know when you want them removed. http://requestform.portal.gc.ca/tickets.html
| |
| | ===Roundtable=== | | ===Roundtable=== |
| − | '''WAGE'''
| |
| − | *GBA+ Awareness week is next week we're hosting an event with CSPS on May 6. Check it out here: https://www.canada.ca/en/women-gender-equality/gender-based-analysis-plus/gba-plus-awareness-week.html
| |
