- Sep 2022
-
kb.wisc.edu kb.wisc.edu
-
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.
-
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.
-
Functionality
ποΈ ~~Functionality~~
I'm guessing no one really uses this language and features probably says enough. Or maybe: "Course List Options / Features"
-
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.
-
click on the
π¬ Click on the what?!
-
Note: the area header and subheader should be utilized with text only.Β
π¬ Callout / highlight this
-
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
-
subject short description and catalog number
π¬ is a space needed?
-
official list on
ποΈ...official list of subject short descriptions under the "Abbreviation" column of...
-
of a subject is
ποΈ ~~of a subject is~~
Could omit this.
-
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.
-
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.
-
Used in Guide.
π¬ No completely clear. The reference feels a circular and unspecific.
-
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.
-
create content
ποΈ~~create content~~ add items OR add rows
-
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 π.
-
when building a course list
ποΈ~~when building a course list~~
Could omit this.
-
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.
-
the location of
ποΈ ~~the location of~~ where you are adding
-
next academic year.
ποΈ...next academic year, where Lumen Programs would list all available and proposed courses regardless of the term.
-