Skip navigation

Feed aggregator

Finding Aids to the Eric L. Berne Papers now available on the Online Archive of California

Brought to Light Blog - Fri, 2014-04-18 09:06

Detailed finding aids for the six collections of Eric L. Berne Papers are now available for researchers to examine on the Online Archive of California. These collection guides provide an in-depth look at the work and writings of Eric L. Berne, M.D. (1910-1970), a San Francisco-based psychiatrist, UCSF lecturer, best-selling author, and father of the theory of Transactional Analysis (TA).

Each finding aid provides a full description of the collection, including dates, background information, scope and content, extent, type of materials, any access restrictions, and a complete box and folder list. The finding aids are all full-text searchable. They can be accessed through the UCSF Archives and Special Collections page or via the Online Archive of California. The following guides have been published:

Eric L. Berne Papers, 1939-1973, MSS 82-0

This accession primarily contains photographs and reel-to-reel audiotape recordings of lectures and meetings of the San Francisco Social Psychiatry Seminars, an organization founded by Berne.

Eric L. Berne Papers, 1931-1970, MSS 89-12

This accession contains a significant portion of correspondence, writings, records of the San Francisco Social Psychiatry Seminars (later the International Transactional Analysis Association), and military psychiatry records.

Eric L. Berne Papers, 1933-1971, MSS 2003-12

This accession primarily contains writings, notes and lectures.

Eric L. Berne Papers, 1929-1970, MSS 2005-08

This accession includes records of Berne’s medical school education, military service, and travels, as well as a significant amount of writings and audio recordings.

Eric L. Berne Papers, 1963-1970, MSS 2013-18

This accession contains 7 recorded lectures by Eric Berne and 44 audiocassettes from the International Transactional Analysis Association Tape Library.

Eric L. Berne Papers, 1904-2007, MSS 2013-19

This large accession includes early personal correspondence, diaries, travel ephemera, educational files, writings, photographs, and artifacts.

These collections are open for research and can be viewed in the UCSF Archives reading room. Please visit this page to make an appointment or contact an archivist: http://www.library.ucsf.edu/collections/archives/access

Digitization work on these collections is progressing quickly. Check back soon for updates on the Eric L. Berne Digital Collection!

Detailed processing and digitization for the Eric L. Berne Papers was made possible by generous support from 17 TA Associations worldwide and many individual donors through the International Transactional Analysis Association.

Categories: Brought to Light

Heartbleed: What you need to know

Mobilized - Wed, 2014-04-16 08:35

 No doubt you’ve heard about the Heartbleed bug affecting countless websites and devices over the past week. Reports of the bug are many, yet information about how it works and what you can do to protect yourself can be difficult to extract from the widespread media response. Here we’ll take a brief look at what Heartbleed is, how it works, and what you can do.

Not a virus, not a breach… so what’s in a bug?

Some of the confusion around Heartbleed is related to the semantics of computer security. If you have owned a personal computer in the last decade, you’re likely familiar with computer viruses that affect your computer’s performance by embedding themselves in your device’s Operating System (i.e. Windows, OSX, etc.) Major data breaches have also made it to the front page of news outlets more frequently in recent years as hackers target user information stored online. In December 2013, Target announced a breach where millions of credit card numbers were stolen. Sony had a similar breach back in April of 2011 where over 77 million accounts were compromised.

Heartbleed is neither a virus, nor a major breach. Unlike a virus, there was no software written with malicious intent. And yet, unlike a major breach, this was not a planned, organized effort to gain access to information. It is actually a flawed piece of code in OpenSSL.

SSL stands for Secure Sockets Layer, a computing protocol designed to encrypt and protect information. This technology was developed so that information could be sent and received privately, without tampering. OpenSSL is just one implementation of the SSL technology, and it can be used to protect data transmission on websites, email servers, chat servers, virtual private networks (VPNs), and more. You may notice a lock icon (see image to right) followed by https:// in your web browser’s address bar when you visit an encrypted website. The s is short for secure and these both signify that the connection is encrypted. Not all websites use encryption, and not all websites employ OpenSSL to achieve encryption. Still, roughly half a million websites use the OpenSSL version that is vulnerable to the Heartbleed bug according to Netcraft’s April 2014 Web Server Survey.

What’s the danger?

So where exactly does this vulnerability occur in OpenSSL? That is as humorous as it is terrifying. Here’s the vulnerable code:  “memcpy(bp, pl, payload);”

Did you catch that? Let’s look a little closer.

Heartbeat to heartbleed

Heartbeat is a term used to describe a connection check done between a server and a client. For context, imagine you are connecting to a server (i.e. a website). The client (you!) will send a heartbeat message to the website, and the website will send it back to you. This response notifies the client (again, that’s you) that the connection is still open and functional. The heartbeat message is useful because it prevents data from being transmitted when the connection is lost, and unnecessary connections can be closed.

If you look again at the vulnerable code “memcpy(bp, pl, payload,)” that’s the heartbeat. The payload part of that code can be manipulated to ask servers for extra information (e.g. usernames, passwords, and other information that was supposed to stay encrypted.) That means a hacker could use the common heartbeat function with a website you’ve visited in the past and exploit the Heartbleed bug to pull back extra data — data that could contain your sensitive information!

The web comic XKCD came out recently with a informative — and humorous — visual take on it. Gizmodo has a far more detailed, but still very understandable, technical overview of the issue.

What should I do?

It is recommended that you change your password on affected sites after they have been patched. Changing your password does not address the underlying vulnerability, so be sure websites have implemented the fix before you make the change.

Mashable has compiled a useful “hit list“ of popular sites where you can verify whether or not you should change your password. Additionally, LastPass has created a tool where you can input a website URL for vulnerability assessment.

You can also review UCSF’s Heartbleed bug information where they mention UCSF MyChart, Mail@UCSF, and MyAccess sites are not vulnerable.

Is my phone or tablet affected?

Apple released a statement last Thursday that they are not employing OpenSSL as the method of authentication for their iOS and OSX platforms, or other “key web services.” You do not need to change your AppleID password unless you use the same password for another service that may have been compromised.

Google’s Android operating system has not employed OpenSSL since version 4.1.1, but Google web services which require login (GMail, Google Docs, etc.) were vulnerable to the bug. You should change your Google account password. Additionally, if you are running Android version 4.1.1, you should check if an update is available for your device.

So many passwords! How to keep track?

We all know the rules. Don’t use the same password twice, make them complex, and change passwords frequently. In the real world, managing so many passwords is incredibly difficult. Remembering these passwords on the go with your mobile device is that much harder.

There are, however, several password managers available that can help with this daunting task. The aforementioned LastPass is a very popular web-based password manager with free and premium options available. The premium option gives access to mobile applications at $12 a year. My personal favorite, KeePass, is an open-source application available on most platforms. You can gain mobile access to your KeePass encrypted database by hosting it in a Cloud Storage provider like Box, Dropbox, Google Drive, etc. LastPass, KeePass, and other password managers can help keep you safe by storing unique, complex passwords in a secure place.

Additional Information

The Heartbleed official site is http://heartbleed.com, and you can find some less technical information in this overview at Gawker’s Non-Geek’s Guide. WIRED  also has an eye-opening review of how this happened and the lesson we should learn from it. Be safe out there, folks.

No related posts.

Categories: Mobilized

UCSF Archives Lecture Series: Lessons at UCSF from the Early AIDS Epidemic, April 16, 2014

Brought to Light Blog - Fri, 2014-04-11 16:13

Join us on Wednesday, April 16th for a special program featuring prominent UCSF faculty. This is the second lecture in a series launched by UCSF Archives & Special Collections.

Learning from Our History: Lessons at UCSF from the Early AIDS Epidemic

UCSF played a leading role in the early response to the AIDS epidemic. UCSF faculty and staff helped create important models of care, made many key discoveries into the nature of the disease and its management, and faced the many emotional and ethical burdens at a time when personal safety could not be assured in patient care. This event will be less a lecture and more a conversation of those early days with four prominent UCSF faculty members, each of whom were present and active from the very first days of what would become a massive epidemic. They will offer their own perspectives on this history and engage with each other and the audience in this program.

Presenters: Drs. John Greenspan, Paul Volberding, Molly Cooke, Jay Levy (UCSF) Date: Wednesday, April 16, 2014
Time: 12:00 pm – 1:15 pm
Location: Lange Room, UCSF Library, 530 Parnassus, 5th floor

This lecture is free and open to the public. Information on how to sign up or donate to AIDS Walk San Francisco will be available before and after this event. AIDS Walk San Francisco benefits HIV/AIDS programs and services throughout the Bay Area, including some at UCSF.

About the UCSF Archives & Special Collections Lecture Series

UCSF Archives & Special Collections launched this lecture series to introduce a wider community to treasures and collections from its holdings, to provide an opportunity for researchers to discuss how they use this material, and to celebrate clinicians, scientists, and health care professionals who donated their papers to the archives.

Categories: Brought to Light

It’s All About Audience

CKM Blog - Fri, 2014-04-11 16:01

Back in February, the new Web Projects Team made known our purpose and guiding principles. All of that still holds true, but we realized that “Support education and meet the research needs of our users regardless of location or device” might need some clarification. UCSF is a somewhat unique academic institution having more staff than students and no undergraduates, among other things. So who is the primary audience that the library supports?

Primary Audiences served by the Library

  1. Teaching faculty
    • usually also involved in clinical research or practice or basic science research
  2. Students in degree programs
    • professional students in medicine, pharmacy, nursing, and dentistry
    • graduate students in basic science
    • graduate students in social sciences, nursing, and history
  3. Researchers in basic science or clinical medicine
    • faculty
    • postdocs
    • PhD students
    • lab managers/research staff

Notice that there is a fair amount of overlap between audiences with some people wearing multiple hats.

Of course there are others who use the Library too, for example, alumni, the public, visitors, Library staff, outside librarians, etc. They can all still benefit from parts of our site, but their needs will not drive decisions about how to structure our web pages and services. Ultimately, everything about the UCSF Library web should make it easier and more intuitive for the three audiences listed above to meet their research and education needs. All else is secondary, though not necessarily unimportant.

UCSF by the numbers

To define these audiences, we began by simply consulting the counts already provided by UCSF. However, those completely ignore Lab Managers and Research Assistants who have many of the same library needs as postdocs. There are also other staff members who do a lot of legwork for faculty, and therefore, reflect the library needs of faculty even though they are not counted as such. And if you talk about “students,” you must realize that the library needs of a medical student are completely different from those of a social sciences PhD. This means that the numbers are a rough estimate for our purposes.

These less obvious realities were gleaned from talking to people. The Library already tends to focus a lot on the Service Desk and subject liaisons when thinking about user interactions. To balance that, we decided to interview a variety of other library employees who act as liaisons to various user segments with library needs. A big thank you goes out to these individuals who took the time to share their super-valuable insights about user work patterns, language, and challenges!

  • Megan Laurance on basic science researchers
  • Art Townsend on Mission Bay users
  • Ben Stever and Kirk Hudson on Tech Commons users
  • Polina Ilieva and Maggie Hughes on researchers of special collections and archives
  • Dylan Romero on those who use multimedia stations and equipment and the CLE

A few other sources of insight came from meetings of the Student Advisory Board to the Library, LibQual feedback, and the Resource Access Improvement group.

We also came to the conclusion that it is helpful to think about users in terms of what they DO rather than by title alone. It’s the nature of their work that really defines their needs regarding library support. Once again the numbers are a rough estimate, but the segmentation they reveal is still helpful.

Next Steps

The Web Projects Team will continue to make iterative improvements to the Library web presence, some small and some larger, driven by our now established Purpose and Guiding Principles and through the lens of our primary audiences.

We will also be regularly checking feedback from end users via usage statistics and quick user tests, and that will in turn, drive further improvements. In addition, we’ll continue to share about the evolution of the Library web and improvements to the user experience. If you have questions or comments on any of this, we’re all ears!

photo credit: Reuver via photopin cc

Categories: CKM

Artificial Eyes in the Artifacts Collection

Brought to Light Blog - Tue, 2014-04-08 09:25

Danz Collection of Artificial Eyes Depicting Diseases and Defects

Pictured above, one of the many beautiful and unusual artifacts in our collections, the Danz Collection of Artificial Eyes Depicting Diseases and Defects. It was donated to UCSF by a local Ophthalmology firm, G. Danz & Sons, Ophthalmic Prosthetics, San Francisco, CA. The date of the collection is unknown, however our best estimates place it pre-1950.

Categories: Brought to Light

RefWorks’ Write-n-Cite Problems with Mac OS Mavericks

In Plain Sight - Mon, 2014-04-07 17:00

If you’re a Mac RefWorks user, and are thinking of upgrading to  Apple’s new Mavericks version of the X operating system, you should be aware that Write-n-Cite is not compatible with OS X10.9.

According to the RefWorks Facebook page, currently, Write-n-Cite only works with OS X up to 10.6.

Without Write-n-Cite functioning you can still format a bibliography using the One Line/ Cite method.

 

 

Categories: In Plain Sight

New feature in PubMed: Clinical trials link to Systematic Reviews which cite them

In Plain Sight - Wed, 2014-04-02 12:25

If your PubMed search turns up a clinical trial, you may see a box linking to systematic reviews which have cited that trial. Not every clinical trial or systematic review in PubMed is included (yet). For now the National Library of Medicine is working on getting each of the 31,000 plus systematic reviews included in PubMed Health linked to the trials they cited.

Screen shot from PubMed

From the PubMed Health website: “PubMed Health provides information for consumers and clinicians on prevention and treatment of diseases and conditions.

PubMed Health specializes in reviews of clinical effectiveness research, with easy-to-read summaries for consumers as well as full technical reports. Clinical effectiveness research finds answers to the question “What works?” in medical and health care.”

For more information about this new feature, see http://www.nlm.nih.gov/pubs/techbull/jf14/brief/jf14_pm_health_blog_trials_sys_reviews.html

Categories: In Plain Sight

Tracking Student Participation in CLE Courses

Convergence - Wed, 2014-04-02 10:00

Understanding how and how often students are interacting with online course material can provide big insights in how engaging a course is and how effectively the students will learn the material. It’s fairly simple to analyze student participation in courses on the CLE with two easily produced reports, the Course Participation report and the Logs.

Course Participation Report

The Course Participation report will give you a summary of how many actions, such as views or posts, were performed by which students in your course. For example, if you want to see how often a student posts to a forum or how many times a student views a page, this is the report you will want to take a look at. Here’s how to view the Course Participation report for a course in which you are enrolled as an Instructor:

  1. Find the Navigation block
  2. Click My Courses (or if you’re already on the course page, click Current Course)
  3. Click the Short Name of the course for which you are interested in seeing the report
  4. Click Reports
  5. Click Course Participation

The interface is fairly simple and you’re given a few options for filtering what data you receive in the report (for example, the particular Activity module, the time period, which CLE role, and which particular actions were taken). Once the appropriate parameters are set, click the Go button and the report will appear on the same page.

You can sort this list by first or last name or by the number of actions. You might want to sort by the number of actions if you quickly want to see the student with the most forum posts for an activity, for example. You can even send a message through the CLE to any or all selected students directly from this page.

Logs Report

The Logs report is helpful if you want to easily get data for one particular student on one or more activities. You can view the Logs report on the webpage or download it in Excel format, so you can do further analysis.

Finding the Logs report is similar to finding the Course Participation report. Just follow Steps 1 – 4 listed above, then click Logs. You can also find the Logs when you are within a given activity under the Settings block.

The interface is similar to the Course Participation report and requires you to filter the data you are interested in viewing. To generate a log, select any combination of group, student, date, activity, and actions, then click the “Get these logs” button. You can see what pages the student accessed, the time and date they accessed it, the IP address they came from, and their actions (view, add, update, delete).

Instructors can decide whether they want students to access their individual activity reports and view their contributions to the course, such as forum posts or assignment submissions. This can be toggled on and off through the Edit Settings on the main course page (Settings block > Course Administration > Edit Settings > Show activity reports).

As you can probably guess, tracking your students’ participation can be really helpful for ensuring student and course success. With a few clicks, you can determine which students have a greater probability of success in the course and which will need extra support, as well as which activities are the most engaging.

As always, check out the CLE Support Center for more tips and tricks on using UCSF’s CLE and never hesitate to contact the UCSF Learning Technologies Group!

Categories: Convergence

Solr/Blacklight highlighting and upgrading Blacklight from 5.1.0 to 5.3.0

CKM Blog - Mon, 2014-03-31 13:22

Last week, I ran into a highlighting issue with Blacklight where clicking on a facet results in the blanking out of the values of the fields with highlighting turned on.  I debugged into the Blacklight 5.3.0 gem and found that in document_presenter.rb, it displays the highlight snippet from Solr response highlighting.  If nothing is returned from Solr highlighting, then it returns null to the view.

when (field_config and field_config.highlight) # retrieve the document value from the highlighting response @document.highlight_field(field_config.field).map { |x| x.html_safe } if @document.has_highlight_field? field_config.field

This seemed strange to me because I couldn’t always guarantee that Solr returned something for the highlighting field.  So I posted to the Blacklight user’s group with my question.  I got a response right away (thank you!) and it turns out Blacklight inherits Solr’s highlighting behavior.  In order to always return a value for the highlighting field, an hl.alternateField is needed in the Solr configuration.

Here’s my code in the catalog_controller.rb that enables highlighting:

configure_blacklight do |config| ## Default parameters to send to solr for all search-like requests. See also SolrHelper#solr_search_params config.default_solr_params = { :qt => 'search', :rows => 10, :fl => 'dt pg bn source dd ti id score', :"hl.fl" => 'dt pg bn source', :"f.dt.hl.alternateField" => 'dt', :"f.pg.hl.alternateField" => 'pg', :"f.bn.hl.alternateField" => 'bn', :"f.source.hl.alternateField" => 'source', :"hl.simple.pre" => '', :"hl.simple.post" => '', :hl => true } ... config.add_index_field 'dt', :label => 'Document type', :highlight => true config.add_index_field 'bn', :label => 'Bates number', :highlight => true config.add_index_field 'source', :label => 'Source', :highlight => true config.add_index_field 'pg', :label => 'Pages', :highlight => true

 

Another issue I ran into was upgrading from Blacklight 5.1.0 to 5.3.0. It does have an impact on the solrconfig.xml file.  It took me a bit of time to figure out the change that’s needed.

In the solrconfig.xml that ships with Blacklight 5.1.0, the standard requestHandler is set as the default.

<requestHandler name="standard" default="true" />

This means if the qt parameter is not passed in, Solr will use this request handler.  In fact, with version 5.1.0, which request handler is set as default is not important at all. In my solrconfig.xml, my own complex request handler is set as default and it did not cause any issues.

But in 5.3.0 the search request handler must be set as the default:

<requestHandler name="search" default="true">

This is because Blacklight now issues a Solr request like this:[Solr_server]:8983/solr/[core_name]/select?wt=ruby. Notice the absence of the qt parameter. The request is routed to the default search request handler to retrieve and facet records.

Categories: CKM

RefWorks Flow: A Free Document Management Tool

In Plain Sight - Mon, 2014-03-31 11:21

Looking for an alternative to Mendeley and Zotero? You’re a RefWorks user but want a tool that’s better suited to collaboration and document management?  You might want to take a look at RefWorks Flow.

 

 

 

 

 

 

 

 

 

 

 

Launched in 2013 Flow is designed to help researchers discover, store, and organize academic articles, citations, and metadata downloaded from electronic databases. and collaborate with other researchers. This cloud-based tool facilitates collaboration by allowing group annotation of articles, sharing of datasets, and group editing of draft documents.

Any student or faculty member with a verifiable academic email address can sign up for a free account, which offers 2GB of cloud storage, and the participation of up to 10 collaborators per project.

View a short online tutorial.

Categories: In Plain Sight

Women’s History Month: The first female graduates of UCSF

Brought to Light Blog - Tue, 2014-03-25 13:40

March is Women’s History Month and, in keeping with the spirit, we’d like to honor a few of the trailblazing women in UCSF’s history.

Portrait of Lucy Field Wanzer

Lucy Field Wanzer became the first woman to graduate from UCSF, then officially known as the Medical Department of the University of California, in 1876. Lucy grew up in Wisconsin and cared for her mother who had tuberculosis during her childhood. This early and significant exposure to the field of medicine convinced Wanzer that she wanted to become a doctor. The family later moved to California, where Lucy fought for the right to realize her dream– her initial application to the University of California program was rejected based on gender. After a lengthy appeals process, she was accepted and the regents adopted a resolution stating that “young women offering themselves for admission and passing the required examination must be received to all the privileges of the Medical Department.”

Medical Department of the University of California, Class of 1876

At the time, a few medical schools on the East Coast had admitted and graduated female students, but none in the West. For the fifty years following Wanzer’s graduation, female students comprised approximately 10% of UCSF medical graduates in the midst of a 4% national average.

Much more has been written about Wanzer elsewhere. For more information, check out the History of UCSF website, this article by a current School of Medicine student, or this extensive paper by a UCSF School of Medicine alumnus.

Blue and Gold, 1890, page 33

 

The next woman to breakdown gender barriers in a UCSF school was Maria Angelina Burch who graduated from the College of Dentistry in 1883. Maria grew up in nearby Pescadero, CA. Burch passed away at the age of 27, just five years after receiving her dental degree. Her obituary, on right, published in the 1890 Blue and Gold, the annual for all of the University of California, refers to Burch as the Dental Department’s ambitious and intelligent “pioneer lady graduate.” Burch established a private practice in San Francisco in 1884 which prospered quickly. She was described as “fast climbing the hill to fame and fortune” at the time of her death.

 

The Graduate, 1912, page 60

Following closely on Burch’s heels was Josephine Eugenia Barbat in the College of Pharmacy class of 1884. Barbat was a native San Franciscan. University records in the 1890′s show that after graduation, Josephine became an instructor of Botany within the College of Pharmacy– no doubt one of the first women to teach the subject, as well. Not quite satisfied, Barbat went on to graduate from the College of Medicine in 1903. She’s listed in the 1904 Directory of Physicians and Surgeons as having a practice at 1310 Folsom St. The 1912 issue of The Graduate, the College of Pharmacy’s annual at the time, features a photograph of Josephine as the President of W.P.A.P.C. (the Women’s Pharmaceutical Association of the Pacific Coast).

The creation of the Training School for Nurses within the University of California in 1907 also served to up the number of women in the field of medicine. Two years later, the school produced its first graduate, Lillian Cohen, pictured below in the unique white mortarboard cap and square blue and gold pin.

Lillian Cohen, 1909

A three-year nursing degree was standard at the time in the Nursing program, and the following year the University of California graduated its first full class.

Training School for Nurses of the University of California, Class of 1910

Today, UCSF celebrates the diversity of its students, staff, and community in many different ways. In 2012, 54% of all incoming students were female. Do you have a favorite woman in UCSF history? Let us know!

Categories: Brought to Light

On Metrics

CKM Blog - Mon, 2014-03-24 16:36

Collecting metrics is important. But we all know that many metrics are chosen for collection because they are inexpensive and obvious, not because they are actually useful.

(Quick pre-emptive strike #1: I’m using metrics very broadly here. Yes, sometimes I really mean measurements, etc. For better or for worse, this is the way metrics is used in the real world. Oh well.)

(Quick pre-emptive strike #2: Sure, if you’re Google or Amazon, you probably collect crazy amounts of data that allow highly informative and statistically valid metrics through sophisticated tools. I’m not talking about you.)

I try to avoid going the route of just supplying whatever numbers I can dig up and hope that it meets the person’s need. Instead, I ask the requester to tell me what it is they are trying to figure out and how they think they will interpret the data they receive. If pageviews have gone up 10% from last year, what does that tell us? How will we act differently if pageviews have only gone up 3%?

This has helped me avoid iterative metric fishing expeditions. People often ask for statistics hoping that, when the data comes back, it will tell an obvious story that they like. Usually it doesn’t tell any obvious story or tells a story they don’t like, so they start fishing. “Now can you also give me the same numbers for our competitors?” “Now can you divide these visitors into various demographics?”

When I first started doing this, I was afraid that people would get frustrated with my push-back on their requests. For the most part, that didn’t happen.

Instead, people started asking better questions as they thought through and explained how the data would be interpreted. And I felt better about spending resources getting people the information they need because I understood its value.

Just like IT leaders need to “consistently articulate the business value of IT”, it is healthy for data requesters to articulate the value of their data requests.

Categories: CKM

A Review of Coursera for iOS

Mobilized - Thu, 2014-03-20 10:56

Within the last few months, Coursera — the online education platform that offers free classes from UCSF and other top universities — released a mobile app for both iPhone and iPad (iOS 7 only). Meant to supplement, not replace, the full desktop experience at coursera.org, the app offers basic features that make it easier to keep up with Coursera classes on the go. Use the app to:

  • view and sync video lectures
  • take course quizzes and other assessments
  • view the course syllabus for your class
  • search for and enroll in other Coursera classes

Easily Watch Video Lectures

The app’s main feature, watching video lectures, works very well. You can either stream the video content on the go, or sync the lectures for offline viewing.

There is a handy “next” button so that you can flip through lectures while in full-screen view, and you can even speed up or slow down the lecture speed while you watch.

To avoid heavy data usage via the Coursera app, you can (1) sync your lectures from a wifi connection and (2) turn off the app’s access to cellular data on your phone. To do this, visit your iOS settings page (Settings –> Cellular) and toggle off Coursera, as shown.

 

 

 

 

Room to Grow

The Coursera app does not currently support discussion forums or peer-assessed writing assignments, two important components in UCSF’s courses. To access these features, you still have to visit the full site at www.coursera.org.

It would be nice if the app integrated quiz reminders and other deadlines into the iOS Notification Center. Similar to the eBay app, which sends a push notification when an auction you’re watching is about to end, the Coursera app could notify you that your quiz is due in 24 hours.

I’d also like to be able to annotate video lectures as I watch them. Since the app doesn’t provide a way to contact the instructor or other students, it would be helpful to enter notes while viewing a lecture. Then, back at my computer, I could post my questions or comments to the class forum.

Lastly, a small complaint: upon searching the iPhone app for the full list of classes offered by UCSF, I noticed that neither “UCSF” nor “UC San Francisco” returned any results. I had to begin typing “University of California, San Francisco” to find the right page.

On the Horizon

According to Coursera’s Mobile FAQ, apps for Android and other devices are currently under development. The mobile team also plans to integrate in-video quizzes in a future release.

Overall, I’m finding this app well designed and useful for watching Coursera’s excellent content on the go. If you’ve tried Coursera for iOS, please share your thoughts in the comments.

Related posts:

  1. Inkling: iPad Interactive Textbooks With all the e-readers and tablets out there, e-books are...
  2. iPads in the Lab: interview with UCSF’s Chandler Mayfield CHANDLER H. MAYFIELD is the Director for Technology Enhanced Learning...
  3. Docphin on Android Looking for a tool to help you keep up with...
Categories: Mobilized

Fiat Lux: Ansel Adams images of UCSF

Brought to Light Blog - Thu, 2014-03-20 09:15

Published in 1967 Fiat Lux: The University of California is dedicated to “those who will make the future.” This book was commissioned by UC President Clark Kerr in the early 1960s. He invited photographer Ansel Adams and writer Nancy Newhall to not only commemorate the past and present of the University, but to project, as far as possible, “the next hundred years.” This was a challenging idea and the authors spent three years touring the nine campuses as well as scientific and agricultural experimental stations, meeting hundreds of people from chancellors to freshmen. Ansel Adams produced 605 fine prints and over 6,700 negatives for this centennial publication that is just 192 pages long and this endeavor almost rivals his body of work dedicated to Yosemite.
At the beginning of the book the authors profiled the campuses or as they were called by Clark Kerr, “Cities of Intellect” and they selected a beautiful panoramic image of the UCSF campus, as viewed from the Golden Gate Park. This photograph together with seven others was also used for the UCSF School of Medicine centennial celebration program in 1964.

University of California San Francisco Medical Center from the tower of De Young Museum, Golden Gate Park, August 1964

The authors of the volume witnessed rebuilding and expansion all around the University, including the UCSF campus where the old medical building that was photographed for the project was demolished in 1967.

Ansel Adams, Clock Tower of old Affiliated Colleges building, with new structures in fog, August 1964

Fiat Lux includes just 5 photographs of the UCSF campus, but there are dozens of others that can be found in the Ansel Adams Fiat Lux collection on the UCR/California Museum of Photography website.

If you would like to learn more about the book, please visit the Bancroft Library website created for the recent exhibit “Fiat Lux Redux: Ansel Adams and Clark Kerr” that featured 50 original photographs selected from Ansel Adams prints in Bancroft’s collection.
The book Fiat Lux: The University of California is available at the UCSF Library.

Categories: Brought to Light

UCSF’s 150th Anniversary

Brought to Light Blog - Thu, 2014-03-20 09:00

Earlier this year the UCSF Chancellor Susan Desmond-Hellman, MD, MPH sent out a message to the campus community announcing key events that will be organized to mark the 150th anniversary of the founding of UC San Francisco. The UCSF’s sesquicentennial celebration will start this year with the Founders Day events in April and continue through May 2015. Additional details can be found on the website that was developed for the 150th anniversary.

UCSF Anniversary Logo

For the past several months the archives staff has been working on several projects that document and bring to life the rich history of UCSF. Our stories about these projects will be accompanied by the UCSF Anniversary Logo, and today we are publishing the first installment from these series.

Categories: Brought to Light

Get an A+ in Using the CLE

Convergence - Wed, 2014-03-19 15:59

Going to graduate school is hard enough, so dealing with how to work in the UCSF CLE should not be on your to do list. New support especially for students is now available on the CLE Support Center!

Some topics of interest include how to receive fewer emails from the CLE, how to customize My Home page, how to enroll in a CLE course, and more! Check them all out and let us know if there’s ever something you’d like included in the list!

 

Categories: Convergence

Headless JavaScript Testing, Continuous Integration, and Jasmine 2.0

CKM Blog - Mon, 2014-03-17 15:29

Earlier this month, my attention was caught by a short article entitled “Headless Javascript testing with Jasmine 2.0” by Lorenzo Planas. Integrating our Jasmine tests on Ilios with our Travis continuous integration had been on my list of things to procrastinate on. The time had come to address it.

After integrating Lorenzo’s very helpful sample into our code base, we ran into a couple of issues. First, the script was exiting before the specs were finished running. The sample code had a small number of specs to run so it never ran into that problem. Ilios has hundreds of specs and seemed to exit after running around 13 or so.

I patched the code to have it wait until it saw an indication in the DOM that the specs had finished running. Now we ran into the second issue: The return code from the script indicated success even when one of the specs failed. For Travis, it needed to supply a return code indicating failure. That was an easy enough patch, although I received props for cleverness from a teammate.

I sent a pull request to the original project so others could benefit from the changes. Lorenzo not only merged the pull request but put a nice, prominent note on the article letting people know, even linking to my GitHub page (which I then hurriedly updated).

So, if you’re using Jasmine and Travis but don’t have the two yet integrated, check out Lorenzo’s repo on GitHub and stop procrastinating!

Categories: CKM

Looking for Health and Medical Statistics?

In Plain Sight - Mon, 2014-03-17 13:48

People are often surprised how difficult it can be to find health and medical statistics. Data collection in the United States is a fairly recent activity and it was not until 1956 that Congress enacted legislation to establish the US National Health Survey in order to collect statistics on disease, injury, impairment, disability, and other health related topics. Data collection and analysis at a national level takes time to compile, so  it is often difficult to find data for the most recent years.

To help you locate statistical information the National Library of Medicine (NLM) has published a new subject guide. It is not designed to be exhaustive but is intended as a pointer to major information sources.

Categories: In Plain Sight

Historic Panoramic Photograph of San Francisco, circa 1933-1935

Brought to Light Blog - Fri, 2014-03-14 09:21

Use our slideshow below to view this beautiful panoramic photograph of San Francisco taken in the 1930s from the Parnassus campus of UCSF. The photograph is comprised of ten discrete photographs taped together to form an almost seamless panoramic image measuring 4.5″ x 54″ looking north and spanning west to east.

Click on a thumbnail to enlarge the images and see the slideshow.

Unfortunately, the photograph lacks accompanying information about its creation, however, several significant qualities have helped us to narrow down the date. Most significantly, in the second portion of the close-ups, on the right side, the unfinished Golden Gate Bridge is visible. The pylons closest to San Francisco can be seen, but not the suspension cables which, according to the Golden Gate Bridge Construction Timeline, puts the image somewhere in 1933-1935.

Other things of note include the presence of the original Kezar Stadium (former home of the SF 49ers and Oakland Raiders), the absence of the Bay Bridge (which was also under construction from 1933-1936), and the generally bare Presidio area.

What strikes you most about the photo? Let us know! We’d love to hear your insights into the old San Francisco landscape.

 

Categories: Brought to Light

Working with Blacklight Part 3 – Linking to Your Solr Index

CKM Blog - Tue, 2014-03-11 09:07

We are using Blacklight to provide a search interface for a Solr index.  I expected it to be super straightforward to plug in our Solr index to the Blacklight configuration.  It wasn’t quite the case! Most of the basic features do plugin nicely, but if you use more advanced Solr features (like facet pivot) or if your solrconfig.xml differs from the Blacklight example solrconfig.xml file, then you are out of luck.  There is not currently much documentation to help you out.

SolrConfig.xml – requestDispatcher

After 3.6, Solr ships with <requestDispatcher handleSelect=”false”> in the solrconfig.xml file.  But Blacklight works with <requestDispatcher handleSelect=”true”>, and passes in the parameter qt (request handler) explicitly .  An example of a SOLR request sent by Blacklight looks like this: http://example.com:8983/solr/ltdl3test/select?q=dt:email&qt=document&wt=xml.

/select request handler should not be defined in solrconfig.xml. This allows the request dispatcher to dispatch to the request handler specified in the qt parameter. Blacklight, by default, expects a search and a document request handler (note the absence of /).

We could override the controller code for Blacklight to call our request handlers.  But a simpler solution is to update the solrconfig.xml to follow the Blacklight convention.

The ‘document’ Request Handler and id Passing

Blacklight expects there to be a document request handler defined in the solrconfig.xml file like this:

<!-- for requests to get a single document; use id=666 instead of q=id:666--> <requestHandler name="document" class="solr.SearchHandler"> <lst name="defaults"> <str name="echoParams">all</str> <str name="fl">*</str> <str name="rows">1</str> <str name="q">{!raw f=id v=$id}</str> <!-- use id=666 instead of q=id:666 --> </lst> </requestHandler>

As the comment says, Blacklight will pass in the request to SOLR in the format of id=666 instead of q=id:666.  It achieves this by using the SOLR raw query parser.  However, this only works if your unique id is a String.  In our case, the unique id is a long and passing in id=666 does not return anything in the SOLR response.

There are two ways to solve this issue.  The first is to rebuild the index and change the id type from long to String.  The other is to override solr_helper.rb to pass in q=id:xxx instead of id=xxx.  And the code snippet is below.

require "#{Blacklight.root}/lib/blacklight/solr_helper.rb" module Blacklight::SolrHelper extend ActiveSupport::Concern # returns a params hash for finding a single solr document (CatalogController #show action) # If the id arg is nil, then the value is fetched from params[:id] # This method is primary called by the get_solr_response_for_doc_id method. def solr_doc_params(id=nil) id ||= params[:id] p = blacklight_config.default_document_solr_params.merge({ #:id => id # this assumes the document request handler will map the 'id' param to the unique key field :q => "id:" + id.to_s }) p[:qt] ||= 'document' p end end Getting Facet Pivot to work

In our index, we have a top-level facet called industry and a child facet called source that should be displayed in a hierarchical tree.    It should look something like:

The correct configuration is in the code snippet below.

#Industry config.add_facet_field 'industry', :label => 'Industry', :show => false # Source config.add_facet_field 'source_facet', :label => 'Source', :show => false #Industry -> Source config.add_facet_field 'industry_source_pivot_field', :label => 'Industry/Source', :pivot => ['industry', 'source_facet']

You must add the two base fields  (Industry and Source) to the catalog_controller.rb file and set :show => false if they should not be displayed.  And it usually is the case since the data is already displayed in the pivot tree.  The current documentation on Blacklight facet pivot support makes it seem like only the last line is needed.  But if only the last line is defined, then the facet pivot will render correctly in the refine panel and it makes you think that facet pivot is working OK. But when you click on the facet, you will get an error, “undefined method ‘label’ for nil:NilClass”:

Categories: CKM
Syndicate content