Change Details

**Problem statement & User Impact** Abstract Wikipedia does not provide the same level of detail when errors occur in article previews as Wikifunctions. As a result, users cannot easily understand why a specific call is failing or where the issue originates. Instead, they have to manually reproduce the error in Wikifunctions to access more detailed information. **Example** Steps to replicate the issue: On Abstract Wikipedia: - Go to https://abstract.wikipedia.org/wiki/Q30 - Change the preview language to Spanish - What happens? ``` Error message result: //Wikifunctions returned a failed response: No matching lexeme for item in language// ``` On Wikifunctions: - Open the replicated function call [[ https://www.wikifunctions.org/view/en/Z26039?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z26039%22%2C%22Z26039K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q30%22%7D%2C%22Z26039K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q3624078%22%7D%2C%22Z26039K3%22%3A%22Z1003%22%7D | here ]] - Click on details - What happens? ``` Error message includes more details: //Errors No matching lexeme for item in language (Wikidata item QID: "Q3624078", connecting properties PIDs: "P5137", language codes: "es")// ``` **Suggested Scope** Enable contributors to access the more detailed error information already available in Wikifunctions when errors occur in Abstract Wikipedia. **Edge cases** While the example above returns a relatively short error message, we need to consider what should happen when error messages are long - keeping in mind that they can also be user generated. **Approach** Approach is open (and we will potentially have to review scope as well) and will be explored with engineering and design before committing to a specific solution (e.g. displaying more detail in the Abstract Wikipedia interface or enabling easy navigation to detailed error on Wikifunctions, etc). **Additional context** Previous example raised in this task: If you look at a page without valid lexemes (e.g. Q11750 in Spanish), it does not indicate which item the lexemes were invalid for. Users should be able to understand why the specific call is failing and where the issue occurs. //Note: Was not able to reproduce this example//

**Problem statement & User Impact** Abstract Wikipedia does not provide the same level of detail when errors occur in article previews as Wikifunctions. As a result, users cannot easily understand why a specific call is failing or where the issue originates. Instead, they have to manually reproduce the error in Wikifunctions to access more detailed information. **Example** Steps to replicate the issue: On Abstract Wikipedia: - Go to https://abstract.wikipedia.org/wiki/Q30 - Change the preview language to Spanish - What happens? ``` Error message result: //Wikifunctions returned a failed response: No matching lexeme for item in language// ``` On Wikifunctions: - Open the replicated function call [[ https://www.wikifunctions.org/view/en/Z26039?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z26039%22%2C%22Z26039K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q30%22%7D%2C%22Z26039K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q3624078%22%7D%2C%22Z26039K3%22%3A%22Z1003%22%7D | here ]] - Click on details - What happens? ``` Error message includes more details: //Errors No matching lexeme for item in language (Wikidata item QID: "Q3624078", connecting properties PIDs: "P5137", language codes: "es")// ``` **Scope** Enable contributors to access the more detailed error information already available in Wikifunctions when errors occur in Abstract Wikipedia. **Approach** Several approaches were discussed in the comments (see below). We aligned on adding a link that can take the user to the current Wikifunctions detailed error information. * [ ] Build a call to replicate the AW fragment, replacing the Z825 arguments with the current values causing the error (Z825K1: wikidata item, Z825K2: language selected in the preview, Z825K3: today's date) * [ ] Build a link to the top-most function page with call={ ...built call... } url property * [ ] Append error message with link "View details in Wikifunctions" **Why this approach?** Right now, users need to replicate the function call manually on Wikifunctions to access all the information. This approach: - Removes the need for manual reconstruction - Makes detailed error information accessible in a couple of clicks - Is relatively quick to implement **Out of scope / Follow-up** This approach does not make error messages on Wikifuntions more actionable. A potential follow-up will be to support richer, contextual, and actionable error messages, which requires a larger effort (potential approaches are described in the comments). **Additional context** Previous example raised in this ticket: If you look at a page without valid lexemes (e.g. Q11750 in Spanish), it does not indicate which item the lexemes were invalid for. Users should be able to understand why the specific call is failing and where the issue occurs. //Note: Was not able to reproduce this example//

**Problem statement & User Impact** Abstract Wikipedia does not provide the same level of detail when errors occur in article previews as Wikifunctions. As a result, users cannot easily understand why a specific call is failing or where the issue originates. Instead, they have to manually reproduce the error in Wikifunctions to access more detailed information. **Example** Steps to replicate the issue: On Abstract Wikipedia: - Go to https://abstract.wikipedia.org/wiki/Q30 - Change the preview language to Spanish - What happens? ``` Error message result: //Wikifunctions returned a failed response: No matching lexeme for item in language// ``` On Wikifunctions: - Open the replicated function call [[ https://www.wikifunctions.org/view/en/Z26039?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z26039%22%2C%22Z26039K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q30%22%7D%2C%22Z26039K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q3624078%22%7D%2C%22Z26039K3%22%3A%22Z1003%22%7D | here ]] - Click on details - What happens? ``` Error message includes more details: //Errors No matching lexeme for item in language (Wikidata item QID: "Q3624078", connecting properties PIDs: "P5137", language codes: "es")// ``` **Suggested Scope** Enable contributors to access the more detailed error information already available in Wikifunctions when errors occur in Abstract Wikipedia. **Approach** Several approaches were discussed in the comments (see below). We aligned on adding a link that can take the user to the current Wikifunctions detailed error information. **Edge cases** [ ] Build a call to replicate the AW fragment, replacing the Z825 arguments with the current values causing the error (Z825K1: wikidata item, Z825K2: language selected in the preview, Z825K3: today's date) While the example above returns a relatively short error message,* [ ] Build a link to the top-most function page with call={ ...built call... we need to consider what should ha} url property * [ ] Appen whend error messages are long - keeping in mind that they can also be user generated. with link "View details in Wikifunctions" **A**Why this approach**?** Approach is open (and we will potentially have to review scope as well) and will be explored with engineering and design before committing to a specific solution (e.g.Right now, users need to replicate the function call manually on Wikifunctions to access all the information. This approach: - Removes the need for manual reconstruction - Makes detailed error information accessible in a couple of clicks - Is relatively quick to implement **Out of scope / Follow-up** This approach does not make error messages on Wikifuntions more actionable. A potential follow-up will be to support richer, contextual, displaying more detail in the Abstract Wikipedia interface or enabling easy navigation to detailedand actionable error on Wikifunctionsmessages, etc).which requires a larger effort (potential approaches are described in the comments). **Additional context** Previous example raised in this task:ticket: If you look at a page without valid lexemes (e.g. Q11750 in Spanish), it does not indicate which item the lexemes were invalid for. Users should be able to understand why the specific call is failing and where the issue occurs. //Note: Was not able to reproduce this example//