20 Matching Annotations
  1. Sep 2022
    1. Table help

      πŸ’¬ Help is needed for sure. This is easily one of the most convoluted processes in the campus Guide solution. No fault to this KB for trying.

      I think a typical user would not see some of this content as "tables," so I wonder about restructuring this to go into use cases.

    2. Course List Functionality/Features

      πŸ’¬ Screenshots for how each of these look when implemented in Guide would be very, very helpful.

      These features / options are a sticking point in working with tables in course leaf.

    3. Functionality

      πŸ–‹οΈ ~~Functionality~~

      I'm guessing no one really uses this language and features probably says enough. Or maybe: "Course List Options / Features"

    4. See below to see how this changes how courses display.

      πŸ’¬ I might lead this section with the screenshot showing the options, then the examples of what the look like followed by the explanation text.

    5. click on the

      πŸ’¬ Click on the what?!

    6. Note: the area header and subheader should be utilized with text only.Β 

      πŸ’¬ Callout / highlight this

    7. Frequently, text is erroneously entered with the 'Quick Add' feature, but the software reads that as a course and will create a 'red-boxed' text.

      πŸ’¬ Callout / highlight this

    8. subject short description and catalog number

      πŸ’¬ is a space needed?

    9. official list on

      πŸ–‹οΈ...official list of subject short descriptions under the "Abbreviation" column of...

    10. of a subject is

      πŸ–‹οΈ ~~of a subject is~~

      Could omit this.

    11. 1c.When all the courses needed are populated, click the green 'OK' button to close the table editor.

      πŸ’¬ Something in here stating that all the options for an row/item in the table will be described later in this article, or in another article - would help here.

    12. Help not included in this document.

      πŸ’¬ Fair enough. This seems to suggest that there is help elsewhere. Is there? I suspect there is not - in which case maybe a statement reading: not typically implemented, consult with guide people for more information around use case and implementation.

    13. Used in Guide.

      πŸ’¬ No completely clear. The reference feels a circular and unspecific.

    14. The following are used.

      πŸ’¬ A definition of each of the typically used table types could be useful. Some examples would be great. Another architecture for this information might break each type out into a separate article.

    15. create content

      πŸ–‹οΈ~~create content~~ add items OR add rows

    16. Building

      πŸ–‹οΈ~~Building~~ Creating OR Inserting

      πŸ’¬ When and where would you do this? Examples? E.g. Inserting a course list in... IDK where else you would put a course list expect in the requirements tab πŸ˜†.

    17. when building a course list

      πŸ–‹οΈ~~when building a course list~~

      Could omit this.

    18. of a subject for the listing of all courses in a specific subject

      πŸ–‹οΈ~~of a subject for the listing of all courses in a specific subject~~ for the course.

    19. the location of

      πŸ–‹οΈ ~~the location of~~ where you are adding

    20. next academic year.

      πŸ–‹οΈ...next academic year, where Lumen Programs would list all available and proposed courses regardless of the term.