Skip navigation
All Places > System Administrator Community > Blog

I take no credit for the content of this blog post. The work involved here is all Santiago Vanegas and going forward I'm going to get him to write his own blog posts with these nuggets in.

 

One of the things we've heard quite a bit when customers start doing simple changes to their login pages like uploading the institution logo is frustration that the default login page does something funny to logos if they don't fit a certain shape/size and you can end up with a login screen that looks something like this.

 

Now, this is actually really simple to fix by uploading a custom login page with some simple custom CSS.

 

By default, the CSS applied to the logo on the page looks like this:

.bb-login .new-logo.customized-logo img {
   width: 15.625rem;
   height: 15.625rem;
   border-radius: 7.8125rem;
}

In an Ultra enabled environment we have no way to get at this at source to make the change. Instead, we need to navigate to the brands page of the environment and download the login-ultra.jsp file so we can add some custom CSS to resolve the issue.

 

The CSS we need to add to the file looks like this:

.bb-login .new-logo.customized-logo img {
   width: 15.625rem;
   height: auto;
   border-radius: 0;
}

 

We add this to the file in between the end of the <bbNG:jsBlock> and before the cookie disclosure. Note that we have also had to add the <bbNG:cssBlock> to the file to add our custom CSS which is not there by default.

 

Depending on your logo you could add a max-width or a 100% width. In this case we’re giving an exact width for the logo to display at an exact size on the login block.

 

This means we get something which looks far more sensible (Yes - I know the logo now looks just like the normal login page now but it is a change I promise )

 

I've attached an example login-ultra.jsp file with the change in it. Hope this helps.

We are happy to announce that the Learn Migration Information Gathering Building Block has been updated to provide Ultra Base Navigation and Courses compatibility/equivalency information.  Install the Building Block (v1.4.1 or higher) for a personalized report of compatibility/equivalency based on the Building Blocks in use at your institution.

 

The Information Gathering Building Block is used when planning for a move to Learn SaaS, but it can now also be used by SaaS customers to help inform a decision to switch Ultra on.

 

Download the latest files:

 

You can access the compatibility reports from the Administrator Panel after the building block is installed and enabled. In the Tools menu, select  Learn Migration Information Gathering  to get started. From there, you can view the report within Learn as part of Main Report – view online, or download via the Building Blocks link under Main Report – CSV download. The CSVs can be imported into the Information Gathering workbook.

 

For more details on preparing for a move to SaaS, please see  Information Gathering for Learn Migration on Blackboard Help, or if you are already using Learn SaaS and are ready to move forward with Ultra, please see Adopting Ultra.  There’s also lots of useful information and resources at https://learnultra.blackboard.com.

 

If you have any feedback on the compatibility/equivalency information provided by the Building Block we would love to hear from you!  Please post any comments or questions below.

Good afternoon, 

 

If you are interested in REST, but don't know how to get started this is for you. I've created a shareable notebook with all steps needed to go from NO REST experience / integration to making a call against your own Blackboard Learn.  It should only take you 20 minutes, tops. 

 

At DevCon, I presented on using REST APIs and helped a few people get setup and make calls against their own Blackboard.  I combined my presentation with materials provided by Blackboard to walk you through every step.  You will need to create a developer account, and have admin access to complete all the steps. You don't need to install any programming language, or know how to use a terminal... at all.  You need to be able to hit play buttons, which will run parts of the code line by line.

 

All of this is available here: 

https://colab.research.google.com/github/mdeakyne/BbRestExamples/blob/master/0.%20DevCon.ipynb 

 

This updated notebook should have EVERY step you need to go from nothing to making calls and exploring. Hope this helps someone get started with REST, so you can build some cool things or write some cool scripts and then share back with the community.  

 

Let me know if you have any questions or comments, and I'll do my best to answer.

 

-Matt

I've written before about guest access to Original courses in Ultra Navigation.  This post is about self-registration in Ultra Navigation.  The expected behavior in the system is:

 

1. Enable self-registration in the specific course in Administrator Panel

2. Share a link to the course with students who are not enrolled in the course

3. When students access the link, and Enroll button is visible in bottom left

 

enroll

 

As long as students are already logged in, authenticated, the system works as expected.  However, this is only one scenario for using self-registration.  Another scenario is to include a link to the self-registration course on a public website or in an invitation email, so students can click on the link, login, self-register, and participate in the course.

 

This scenario in Saas systems with Ultra Navigation breaks down.  After students click on the link, they are asked to login, and then they are forwarded to the Institutional Page ( Home page ).  This means that they have to click again on the invitation link to see the enrollment option.

 

In the past a solution was to enable guest access on a single course item, such as the Welcome content area in the course, and have students be logged in as guest, upon clicking Enroll, they would be asked to login as themselves and participate in the course.  This produces an error message.

 

So, to the workaround/solution. 

 

The invitation link has to be crafted to use the default login page and skip custom login page with appropriate new_loc parameter.  It may sound complicated, but the basics are here:

 

1. Destination URL to the self-registration course:

https://uic.blackboard.com/webapps/blackboard/content/listContentEditable.jsp?content_id=_5297212_1&course_id=_119729_1&mode=reset 

 

You would find this URL by right-clicking on the content area in the destination course.

 

2. Encode the destination URL in a new URL with new_loc parameter:

https://uic.blackboard.com/webapps/?action=default_login&new_loc=%2Fwebapps%2Fblackboard%2Fcontent%2FlistContentEditable.jsp%3Fcontent_id%3D_5297212_1%26course_id%3D_119729_1%26mode%3Dreset 

 

3. Create a short URL, easy to remember:

http://bit.ly/uiccareerready3

 

If step 2 seems a bit challenging, I'm sure the nerd-readers know what's going on, you can use our Guest Link tool to generate the URL.  All you need is the destination URL from step 1, then paste it in the Guest Link tool.  Simply, generate the guest URL, then modify one element:

 

action=guest_login

to

action=default_login

 

The resulting URL will present the default login page (utilize ldap, shib, or local auth), then lead the student to the course with Enroll link.  After clicking Enroll the student will be able to participate in the course.

Ultra Navigation is a wonderful feature, which is a modern gateway to online learning with Blackboard.  Would you like to add more resources in the Tools area or grant to those resources access to students or faculty by role?  You can do this with a flexible LTI links and the Institutional Page Helpful Links.

 

This may facilitate an easy transition from the Blackboard Community System Portal to Ultra Navigation, and become a better experience for faculty and students.

 

Do faculty have difficulty finding their courses in the term-based display?  Do you have a Viking spirit to raid the features of Ultra Navigation?

 

You can now use the LTI Tool Generation app to connect regular URLs or special tools to Ultra Navigation or Ultra course tools section.  The Wizard itself is an LTI tool and takes 3 steps to configure. 

 

1. Register the LTI tool domain and approve on your system

2. Follow the steps to create LTI placement URLs

 

Some examples of resources, which can be turned into Ultra tools:

1. Your web pages with documentation and existing resources (ex: help.blackboard.com)

2. Building Blocks without LTI functionality available (ex: My Courses Plus)

3. Community System tools (ex: tabs)

4. Instructor tools from My Blackboard (ex: Retention Center for multiple courses)

 

1. Community System in Ultra Navigation:

Community System in Ultra Navigation

 

 

 

 

2. Link to documentation or introductory resources:

Documentation link to Blackboard Collaborate

 

 

 

 

 

3. Embed Building Block content or modules to use in Ultra Navigation or Ultra courses under Books & Tools (ex: My Courses Plus):

My Blackboard Plus building block

 

 

 

 

ex: Qwickly for instructors:

Qwickly for instructors

 

 

 

ex: Qwickly for students:

qwickly for students

 

 

 

 

4. Link to tools from various Blackboard areas such as the multi-course view of the Retention Center from My Blackboard:

Retention Center in Ultra

 

SPECIAL NOTE REGARDING FORWARD-LOOKING STATEMENTS OR COOL THINGS THAT MAY OR MAY NOT WORK ON YOUR SYSTEM

 

This prospectus contains forward-looking statements that involve substantial risks and uncertainties. You can identify these statements by forward-looking words such as “anticipate”, “believe”, “could”, “estimate”, “expect”, “intend”, “may”, “plan”, “potential”, “should”, “will” and “would” or similar words. You should read statements that contain these words carefully because they discuss our future expectations, contain projections of our future results of operations or of our financial position or state other forward-looking information.

 

In other words, any elements discussed above can be discontinued by any of the vendors at any time.

 

Setup demos:

 

gifretention

 

 

icon

LTI Tool app

How important is guest access to your school?

 

After our Saas migration a strange thing has appeared.  Our system no longer allows guest access.  It appears, with Ultra navigation, this is by design to Original or Ultra courses.  The guest URLs now redirect to the login page instead of starting a guest session.  As a result, guests are unable to view guest allowed content.

 

This may be a bug related to article 000043671 or another issue, but for now we are given a workaround to modify guest URLs.  An example of a URL that should work as guest:

 

https://uic.blackboard.com/webapps/blackboard/content/listContentEditable.jsp?content_id=_5297212_1&course_id=_119729_1 

 

The workaround calls for encoding the original url and adding it as new_loc in a new URL.

https://uic.blackboard.com/webapps/?action=guest_login&new_loc=/webapps/blackboard/content/listContentEditable.jsp%3Fcon… 

 

Notice action=guest_login and new_loc=...

 

Hopefully this will be resolved soon as most instructors expect guest content to be available via the same URL as logged in users.  However, for now we have a URL generator that will take your old URL and encode the URL to create a working link.

 

link

Guest Link App 

As I mentioned in my May blog post, we will be replacing the New Box View experience for Inline Assignment grading for both the Original and Ultra experiences.  If you haven't read my previous post yet, I recommend reading it first and coming back.  Over the last several weeks, we’ve continued the technical review of a replacement tool that compared building our own in-house tool and various 3rd party technologies.  We have decided on the direction of the New Box View replacement and will be partnering with a vendor to bring richer functionality and new features to the Inline Grading experience.  This not only will bring the experience more in line with the features that Crocodoc had available, but also delivers additional features that will be beneficial to the grading workflow.   

 

You might be asking why we decided to embark on a partnership with another vendor.  With this integration, we will have complete ownership of rolling out upgrades, fixes and improvements.  Their sleek design, ease of use and expanded feature set were key factors to filling in the gaps for much needed functionality. There is flexibility for us to extend the feature set and layer additional customizations on top of the user interface at a much faster pace as well.  I would love for your first experience with the replacement tool to be through a Learn environment, so I won't be sharing the vendor's name yet.  In the mean time, I can confirm enhancements you will be seeing with then new solution.  While I could easily create a top 20 list, here are the top 10 annotation capabilities you can expect to see with initial release.  

 

  1. Users can add a comment and then customize the color or icon associated with the comment.  
  2. Text can be added directly on the page and modified to use different colors, size and font.  
  3. There is a sidebar summary view that lists the type of annotation by page, text from a comment, and the ability to delete an annotation.  
  4. When highlighting or freehand drawing, there are different color and size selections. 
  5. Annotations can be edited, moved or deleted easily. 
  6. There are options to strikethrough text and users can underline with either a straight or squiggly line using different colors.  
  7. Freehand highlighting and drawing can be erased.  
  8. When downloading or printing, the annotations are automatically built into the document. 
  9. There is a thumbnail view for each page in the document. 
  10. The menu is responsive on smaller screen sizes and users can seamlessly switch between touchscreen and a mouse on a device.  

 

While we needed to complete a technical review for the replacement, we are continuing the technical due diligence to ensure the migration is not only seamless but ensuring clients have enough time to prepare and plan for the release.   We are looking to make it generally available without any downtime requirements and need to make sure all the pieces are in place to make that happen.  Additionally, we understand a major shift during the middle of a term is not ideal so we will be gathering client feedback to identify an optimal time for the release.   

 

A lot of clients have already expressed interest in how they can help with testing and feedback, so there will be several options to provide input.   We plan to have a Technical Preview Program ahead of the release and will have several opportunities starting next month as well.  The first will be at BbWorld where we will continue to provide more details about the replacement tool.  After BbWorld, I will be attending various meetings, such as the weekly Admin Office Hours, to dive further into the new features, discuss change management and gather feedback.  

 

A big thank you to everyone who has shared recommendations and feedback so far.  If you have any questions, feel free to post them below or send me a direct message.


Thanks,

Julia

I am pleased to share today what we're planning for the future and appreciate all of the feedback regarding the current functionality with the New Box View experience. When Box acquired Crocodoc, we believed that Box would continue to deliver functionality and enhancements for these critical teaching workflows, but that has not been the case. As many of you know, we worked diligently with Box in an attempt to get better results.  Based on the lack of responsiveness, quality control issues, and with your feedback and input (which accelerated our thinking on how we must improve your experience in this area), we have decided to replace New Box View and move forward with a new solution that is more in our control in order to better meet your current and evolving needs. 

 

I also wanted to share a bit more about the timing of this message. In the last couple of months, we were trying to work with Box and were in the middle of negotiating the immediate partnership agreement which is why we did not share as much as we would have liked. At the same time we were beginning technical diligence while building out more robust requirements with your feedback. The list of enhancements gathered on the Community site have been a beacon throughout the process for what needs to be included in the future workflow for both Original and Ultra.  We need to not only deliver the core features you appreciated with Crocodoc but also add innovative functionality as well.  We are currently continuing the technical diligence, gathering your feedback on requirements and prioritization, and deciding upon the best architecture and solution that will provide the ability to be dynamic and innovative as your needs change over time. To be honest, this is not easy work to get right, and we need this analysis done in order to share a more definitive timeline.  We will share more details on timing and functionality in mid-June, and then again during BbWorld.  As we work towards the release, we will be providing regular updates on the progress as well as targeted outreach for feedback opportunities, so you'll be hearing from me or others working on the project for input.

 

So as you can see, we’re set on moving in a new direction with this critical capability.  As we go through this process, we are not going to stop working with Box to push for innovation in New Box View based on your needs.  While we can’t predict how successful this will be, we understand that you’ll being using New Box View for Inline Grading in the near term, so we want to make sure this experience is as good as it can possibly be.

 

I want to say a big THANK YOU for your ongoing engagement on the Community site and elsewhere.  We know that this has been a challenging topic, but I hope this update, and our updates going forward, will help give you clarity and confidence about the improvements coming in this important area.

About: Internet Explorer and Blackboard Learn don't play nice together. This article explains how to create a warning that will appear only for users who attempt to log in to your Blackboard environment using Internet Explorer.

 

What's the Problem?

For the better part of my career as an LMS administrator, I've told anyone who would listen that Internet Exploder (Explorer) is good for only one thing; downloading a different browser. While I've seen many people abandon the little blue "e" for a more modern browser, there remains a coterie of diehard IE adherents who simply refuse to switch.

 

In their defense, there are plenty of reasons folks may still be on IE. Some are running old machines. Some lack (or think they lack) the technical knowledge needed to update their browser. Others are comfortable with the way things are and just don't want to change. Whatever the reason, (and I'm sure the reason is a very good one), it's time for a change. It's 2019. Microsoft officially ended support for Internet Explorer three years ago, and the old blue "e" just ain't what it used to be.

 


Why Now?

 

Deep in the heart of the Learn SaaS v3500.0.3 Flexible Deployment release (roughly equivalent to v3500.9.0 for Continuous Delivery), something changed, rendering useless some functionality for Internet Explorer users. Since the release of 3500.0.3, we've received calls from frustrated IE users for whom the platform no longer functioned properly and we had to break the bad news to them that the only way to fix their problem was to stop using Internet Explorer.

 

But it's far better to catch these users before they log in to the system so that they aren't in the middle of something when they realize that there is an issue.

 

To help minimize frustration for our end users, we created an "Incompatible Browser" warning that appears on the login page. We didn't want to do was use the login page announcements area (because these messages cycle through) or display the warning to users who were already on a compatible browser.

 

So we had to come up with a different solution...

NOTE: If you're working with a single sign-on portal that bypasses the Blackboard login page, you might as well stop reading here, contact your portal admin and ask for their help in creating an appropriate intervention for IE users.

 


Danger, Will Robinson! Danger!

 

Still with me? Cool.

 

Our solution to this issue was to create a warning. It's only a warning. It doesn't force anyone to do anything, but it provides users with critical information based upon their system configuration, explains the problem and provides instructions on how to correct the issue.

 

The warning is designed so it will only be seen by IE users but will not prevent them from logging in. It is also configured so that it cannot be dismissed by the end user.

 

Since we're writing code for old browsers, we want to keep it as simple as possible and avoid using JavaScript or other elements that the browser might not recognize or render properly. So, the simplest solution is one that is 100% CSS and HTML.

CAVEAT: Each institution's login page is configured differently. Before beginning, make sure you have a backup copy of your login page downloaded to a local machine. When you go to test your changes, make sure you're logged in to your environment in a separate browser from the one through which you're uploading the updated .jsp file. This way, if you accidentally insert code that breaks your login page, you can still change it back to the previous version.

To Catch IE (or, the part you want to go to if you skipped all that intro text)

 

To ensure that you get all the IE users, you have to approach it from two different directions, because in the world of Internet Explorer, there are two different technologies. Newer versions of Internet Explorer (10 and up), can be identified by using a media query. Old versions of Internet Explorer (9 and earlier) can be detected with a conditional comment (something that was abandoned after version 9).

 

First Things First

Both technologies will display the same warning. So we're creating a <div> element and making it visible when certain conditions are met. Before we worry about how to make it visible, we need to first create the element and hide it. To do this, I opened the login.jsp file and found the CSS section. After the main components were configured, I added the <div> element and set it to be hidden by default. It looks like this...

 

#IEMessage {

display: none;

}

 

 

Media Queries

I mentioned that there were two different ways we had to approach this. The first is the more modern media query method to detect IE10 and higher. I'm not going to go into what media queries are (you can do that research on your own), but suffice it to say that it's a little piece of CSS that says to the browser, "Hey! If you can interpret this code, please use these parameters. Otherwise, ignore it." In this case, all browsers EXCEPT for Internet Explorer will look at the code and be like "I have no idea what you're talking about. I'm ignoring you." You can add this at any point in the CSS, because CSS isn't compiled code and it isn't rendered in any particular order.

 

The @media all and (-ms-high-contrast: active), (-ms-high-contrast: none)media query tells the browser to display the div ONLY IF the stated conditions are met, and since -ms-high-contrast is a setting that only pertains to IE 10+, it will be ignored by everything except IE10+. The most important setting is display: inline-block; part because that's what tells the browser to make it visible (there are options other than inline-block, but I'll let you research that on your own). The rest is purely cosmetic.

 

 

@media all and (-ms-high-contrast: active), (-ms-high-contrast: none) {

#IEMsesage {

border: 4px outset #EAEAEA;

display: inline-block;

margin: auto;

position: relative;

text-align: center;

width: 70%;

max-width: 600px;

background-color: #FAEBD7;

color: #CCCCCC;

}

}

 

Conditional Comments

Conditional Comments only work on IE9 and older versions. Conditional comments are statements that go in the HTML part of the page (not the CSS) and should immediately follow any <meta> tags. The conditional comment, similar to the media query, says to the browser "Hey! If you can read this, do this. Otherwise, ignore it." To take your CSS from the media query and put it into the conditional comment, just paste everything from the #IEMessage div into the space between <style> and </style> tags.

 

 

<!--[if lte IE 9]>

<style>

 

</style>

<![endif]-->

 

 

Add the <div> to the <html>

The HTML area of the login.jsp file lays out exactly how the elements on your homepage will be displayed. In this part, you WILL need to worry about positioning because these are the content and formatting information that is passed to the browser.

 

In our case, I added the warning above the login options (we have three buttons from which users select their role in our system and are then directed to the login page appropriate to their role).

 

This part contains the actual text of the message, and you can say whatever you want, just make sure it's properly formatted. The key is to create a <div> with the ID of "IEMessage" (or whatever you named the div in the CSS) and insert all your code.

 

 

<div id="IEMessage" style="margin-left: 5px; margin-right: 5px;">

<h1>WARNING!</h1>

<b><i>We have detected that you are using Internet Explorer to access Blackboard.</i></b><br><br>Please note that Internet Explorer is<b>not</b> compatible with Blackboard and may not perform as expected. To avoid errors and frustration, we

<b>strongly</b> suggest that you use a different web browser.<br><br>For best results, we recommend <a href="http://www.google.com/chrome/" target="_blank">Google Chrome</a> or <a href="https://www.mozilla.org/en-US/firefox/new/" target="_blank">Mozilla Firefox</a>,<br> but any of the <a href="https://help.blackboard.com/Learn/Student/Getting_Started/Browser_Support" target="_blank">supported browsers in this list</a> will work as well.<br><br>

If you wish to proceed using Internet Explorer, you may log in below.

</div>

 

Now, all you have to do is save your updated file, upload it into Blackboard and navigate to your login page using Internet Explorer. If it worked, you'll see your message displayed.

 

ie_warning.png

 

To see how it will render under various versions of Internet Explorer, you can click on the cog in the IE menu and select "F12 Developer Tools" from the dropdown. To preview the page as it would be rendered in other versions of Internet Explorer, change the document mode by clicking on the funky little document mode icon (just to the right of "Memory" in the menubar) and selecting which version of IE you'd like to render the page using.

 

iedevtools.png

 

At this point, there are only 3 more things you need to do....

 

  1. Tweak.
  2. Test.
  3. Repeat.

 

Hopefully this made some sense to someone out there.

Update April 3rd: Box reported an incident starting at 1:13 PM EDT which impacted New Box View.  Users might have seen latency and/or errors while using Inline Grading within the last few hours.  The issue has been resolved as of 3:28 PM EDT and service should be fully restored.  If you are still seeing any errors or latency, please let me know.

___________________________________________________________________________________________________________

Update March 28th: Box is postponing tomorrow's release to ensure all of the issues we reported are addressed.  We will be working with them to get an updated timeline and will provide updates as we know more.

____________________________________________________________________________________________________________

Update March 22: In case you weren't able to attend the 9.1 Office Hours meeting, Box is tentatively planning to release an update on March 29th.  We will be testing this release before it is made live to confirm the planned fixes as well as the critical regressions with the last release are fixed.  I'll be sharing more information next week, but wanted to give everyone advance notice of the upcoming release.

_____________________________________________________________________________________________________________

You've probably seen me responding to New Box issues but I haven't taken the time to fully introduce myself.  Some of you may know me from Cumulative Update releases, bug discussions or from our Learn Technical Preview program.  If you were an ANGEL client, you might even remember me from Tier 1 Support. I have been with Blackboard for almost 10 years and on the Learn Product Management team for the last 4.5 years.

 

With Trey's departure last month, I am the new lead with the New Box View integration for Inline Assignment Grading and our partnership with Box, Inc.

 

After researching the past few weeks, I've put together a list of the most requested features and where we need to go with the feature. Based on feedback, this will help bring New Box View in better alignment with the previous Crocodoc workflows and add additional functionality.

 

  1. Sidebar- Summary View- In Progress with Box and targeted for release later in the year.
  2. Editing annotations
  3. Re-usable comments/ Comment Bank
  4. Video based comments and feedback
  5. Strike-through Annotation Type
  6. Different colors for highlighting tool
  7. Different line color and drawing line thickness
  8. Indication of Comment in Highlighted Text
  9. Eraser

 

 

In addition to this list, there are navigational and display elements that need improving as well to enhance usability and flow.  While not considered new features, it's worth noting that these will also be reviewed as we drive roadmap discussions with Box.

 

Also, as we move forward, I will add that it's never my intention to be vague with release timelines when sharing information.  I promise to be open as much as possible with available information.  Part of the conversations we're having with Box is improving timeline communication.

 

Please feel free to leave any additional feedback on this post. Part of the research was reviewing Community site threads, but there is a possibility I have missed some important ideas.  I will be at the Office Hours meeting on March 19th at 12 PM ET that Edgar Gonzalez and Mark Burris host to review and discuss feedback as well.

 

As always, I appreciate the candid feedback and passion around improving this feature so it better fits the needs of users.

 

Thanks,
Julia Miller

Product Manager, Learn

Update: 2/22 - 7 PM ET

 

This is an update to our earlier communication regarding the planned rollback of New Box View to an earlier, stable release.  At this time, Box has informed us that the rollback is complete.  The Blackboard team has confirmed this.  We expect that this rollback has resolved the earlier issues reported and described here.  We are completing initial testing to validate resolution, and as always, if you find any issues have persisted, or if you have reason to believe there is a new issue, please let us know immediately using Behind the Blackboard.

 

Once again, we sincerely apologize for the disruption this release has caused.  We will be providing additional communication in the coming days about additional steps we will be taking with Box to help prevent future incidents from occurring.

 

Update: 2/22 - 6 PM ET


As we shared in our earlier communications on this topic, we’ve been in active communication with Box since these issues were reported.  Given the urgency of the situation, Box is prioritizing work to rollback to an earlier, stable release.  The Box team is assessing the details of this now, and based on their guidance, we expect this rollback to happen tonight, February 22nd, Eastern Time.

 

When the rollback completes, we will share another update to confirm the operation is complete.

 

Thank you for your patience and understanding as we continue working to resolve these issues.

FEB 22 UPDATE: Please refer to this new post for the most recent update regarding a rollback to an early release of New Box View

 

Original Post Below From Feb 21 ---------------

 

Your concerns and frustrations are definitely being heard with regards to the critical bugs introduced this week and we're actively working towards a resolution. Since I'm receiving reports of NBV bugs through various channels, I wanted to use this post as the main location to document the individual issues, shared workarounds and provide updates on timing. I do apologize for not having a timeline resolution at the moment, but Box is actively working on providing those to me after additional discussions today.

 

  1. Highlight Tool: When the resolution is low (below 1600*1200), the browser window is zoomed in or not maximized, the highlight tool disappears.
    1. Resolution Timeline: TBD
    2. Workaround: See silent recording here: Video Link
    3. Related Threads:
      1. new Box view update - no highlights - DRAWINGS DON'T DELETE
  2. Drawings: Once you have added a drawing, the delete tool is missing.
    1. Resolution Timeline: TBD
    2. Workaround: Submit the assignment to save changes, then go back into the attempt, expand the iframe and THEN you can select drawings to delete them.
  3. Comments: When adding a comment, the cursor doesn't automatically appears in the "write a comment" text box.
    1. Resolution Timeline: TBD
    2. Related Threads:
      1. BOX Grading Toolset Travesty
  4. No hardware stylus functions properly (thanks: Amy Eyre and Aderemi Artis) (Was “iPad Pro: Stylus input has stopped working on iPad Pro.

5. Trash Bin Icon

  1. Resolution Timeline: TBD

6. Comment Box Panel

  1. While Box categorized the change in display to be more responsive and currently functioning as designed with the long panel showing to the right, there may still be some inconsistencies in the experience. I'm reading through various threads to see if I can tease out any underlying issues.

 

I also wanted to re-share the document Amy put together as others are finding it helpful. Thanks Amy Eyre!

New Box View - Staff - "Small Screen" Workaround Guidance - Google Docs.

 

While there are still outstanding issues that need to be solved, the focus right now is tackling any new critical items found with the update this week as quickly as possible. I am compiling a list of any outstanding bugs and enhancements to start tackling next.

 

Thanks,
Julia

 

2/22 Update: While we don't have timelines yet, I wanted to share an update on the status for a portion of the items. The ability to delete annotations (#2) is actively being worked on by Box engineers. The missing highlight capabilities (#1) and the cursor automatically populating in the text box (#3) are still being investigated further. Regarding the trash bin icon (#5), the current behavior is expected to better match other Box behavior, however they are discussing reverting the current behavior.

Thanks everyone for all your comments and feedback to this post so far. I am reviewing all of them to capture additional bugs and feedback for Box.

A feature in Blackboard called Goals allows faculty and departments to collect information for accreditation or other purposes as to how programs and curriculum aligns with course goals.

 

Faculty can align course content and assessments (eg. discussion forums and threads, blogs, journals, tests and individual questions, assignments, and Grade Center columns) to one or multiple goals.

Reports can then be run that display how students are performing in alignment with the associated course or department goals.

 

Many reasons cause departments to seek continuous quality improvement in program and course curricula. In the School of Computing and Information Systems at GVSU, there is a need to effectively support accreditation requirements as well as to focus on the improvement of the student experience. To this end, the department designed an assessment plan that involves all faculty around the following claims:

  1. We know what we do
  2. We do it well
  3. We can prove it

 

A number of assessment tools can be used in collecting data and evidence in the improvement program such as:

  • Senior exit survey
  • Focus Groups
  • Internship supervisor survey
  • Comprehensive exit exam (standardized or local)
  • Student portfolios evaluated by committee
  • Faculty self-reflection about each course
  • External evaluators of student performance
  • Performance criteria within each course

 

As part of the program faculty collect samples of student work. This may include making copies of each assignment and exam with representation for student high, average, and low performance. The criteria for student performance should be measurable, defined by observable behavior, and identifying a specific standard (or minimum standard).

The Blackboard Goals feature allows instructors to mark assessments or content in Blackboard Learn courses as performance criteria to reach a curriculum goal. While the curriculum goal does not have to be the same as a course learning objective, they often overlap. In turn, Blackboard Learn collects student scores and compares them to set target performance level and average range. This helps in identifying students who meet expectations or are outside of them.

 

The resulting Blackboard course performance report summarizes how students met the expected performance criteria against one or more set goals. The course itself can be archived or copied to retain assessment artifacts and assignment samples. The report is granular enough to provide a breakdown of academic performance per student on each assessment and curriculum goal. The following sample reports come from Introduction to Computing, CIS 150.

 

courseoverviewgoals.jpg

studentgoalreport.jpg

 

Overall, the Goals feature in Blackboard Learn is a very useful tool for collecting academic data and including it in a larger, final report submitted for each course, which includes faculty reflections, student evaluation samples, assessment of previous adjustments, and proposed changes for the future.

 

Thanks to Eric Kunnen for his ongoing support of key instructional projects.

 

How to Run a Goals Report - YouTube

Original post at GVSU

 

Thanks Chris Bray for the Blackboard Learn Goals XML Generator!

 

http://ftc1.uark.edu/~cbray/goals2/

 

Here are the details:

Generates XML files that can be imported into Blackboard Learn for use with Goals, based on the documentation at help.blackboard.com

 

Notes:

Example Files:

eschramke

Bb Grader Announcement

Posted by eschramke Jan 25, 2019

Effective March 29, 2019 the Blackboard BbGrader App will no longer be supported.   


Bb Grader will be removed from the Apple App Store and support will cease to service on March 29th, 2019 in all markets.  This discontinuation furthers the progress we’ve made across our product portfolio to simplify, consolidate, and promote our next generation solutions. 

 

As a part of our commitment to delivering a portfolio of high-quality products to help our clients thrive in a complex and changing educational environment, we’ve planned a robust roadmap that continues to build upon the grading capabilities already available in Blackboard Instructor to provide instructors the best classroom experience while on the go.

 

To learn more about grading in the Blackboard Instructor app, please visit https://help.blackboard.com/Blackboard_Instructor/Grading.

stolleb

Calling All System Admins!

Posted by stolleb Jan 24, 2019

Have your say in the evolution of the System Admin Panel in Blackboard Learn Ultra!

 

As part of our continued commitment to research, design and iteration in Learn Ultra, we want to hear more about how you currently use the Administrator Tools page in Learn. What features do you use? What works well--or doesn't? What would you change? We'd appreciate your input, even if you don't currently use the Ultra experience.

 

Help shape the tools you use to deliver and support Blackboard Learn at your institution by filling out this survey: Blackboard Admin Panel Survey (The survey should take approximately 10 minutes to complete.)

 

Thanks for helping inform the future of Blackboard!