Truncation suggestion #1347
-
|
Paste guidelines suggest that -- "Truncation should NOT be used on page headers, titles, labels, error messages, validation messages, notifications, or SIDs." Can team have any guidelines on for a report that has 3 different types of SID as data entry? Our existing reports truncates SID in the center and we like to continue using that style. Also SID is not important to users. Users wants and needs ICCID for reference and that is not truncating.
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 6 replies
-
|
@ishah-twilio Our truncation guideline around SIDs is mostly because there are a number of use cases where customers need to copy-and-paste SIDs into other parts of the Twilio product, command lines, etc., as well as verify that they're identifying the right object with a SID. However if you know that one of the SIDs you have listed isn't important to users, are you able to remove it? If the Command SID is the only unique identifier for that table row, it's also probably fine to truncate if you know that customers will never need to see or interact with the whole string of text. |
Beta Was this translation helpful? Give feedback.
-
|
@ghostling sure! We can definitely update the guidelines. How's something like this?
|
Beta Was this translation helpful? Give feedback.
-
|
Yes that's fine, but currently the Truncate component only cuts off the end and appends ellipsis. I don't see a way to truncate the middle of a long string. 🙁 |
Beta Was this translation helpful? Give feedback.
-
|
Ah, got it. Let me chat with the team! For some context, is there a reason customers need to see both the first and last few characters, and not just the first or last character? |
Beta Was this translation helpful? Give feedback.
-
|
I just have anecdotal evidence from the past 5 years of watching Twilions use SIDs internally and have been watching people use either first few or last few. Personally I use last few 🤷♀️ , but would be something good to key an eye out for... |
Beta Was this translation helpful? Give feedback.
-
for me (and i'm sure for others consciously or subconsciously), it's to ensure uniqueness that this is the SID you're looking for. Github agrees that truncating is fine, if there's enough characters to guarantee that uniqueness :) f10e615 (full URL) |
Beta Was this translation helpful? Give feedback.
-
|
For IoT Super SIM usecases, Customers never really use the SIM SID at all. Not to look at for any reason we discovered in the phase of research. We have interviewed 20+ customers in the year of 2020 for various usecases and all of them have said give me ICCID and don't force me to use the SID. SIM SID it Twilio's internal identifier and ICCID is the most commonly used identifier for SIM in the industry. It is more likely that customer will copy and paste the ICCID than the SIM SID. For this table -- Command logs feature Command SID is the unique identifier. So it should/could be displayed in full. Though during the usability studies customers were ok to scan through the truncated list and click on the link for details. We like to truncate the SIM SID in the middle to allow customer to scan the uniqueness if necessary. And we will monitor the support tickets and customer ask in future research studies if necessary. User will more likely copy the ICCID than SIM SID. To avoid the accidental clicking on the link we like to not link the ICCID. Details page displays the full SIM ID / ICCID. |
Beta Was this translation helpful? Give feedback.
-
|
@ishah-twilio @ghostling @vnguyen94 Thanks for all the input! Since the current component is truncating based on width, rather than character count, it's going to take us a little more digging into use cases to figure out:
^ This is true for both truncation at the end and start of a string, but gets even trickier with middle truncation. For now, we recommend applying your own truncation for your product, and we'll take note of this use case for our next iteration of the Truncation component. |
Beta Was this translation helpful? Give feedback.
@ishah-twilio Our truncation guideline around SIDs is mostly because there are a number of use cases where customers need to copy-and-paste SIDs into other parts of the Twilio product, command lines, etc., as well as verify that they're identifying the right object with a SID.
However if you know that one of the SIDs you have listed isn't important to users, are you able to remove it? If the Command SID is the only unique identifier for that table row, it's also probably fine to truncate if you know that customers will never need to see or interact with the whole string of text.