Autor: Münster, Joseph Joachim Benedikt, 1694-1751
Erschienen 1751
BSB-Signatur 4 Mus.pr. 44603

URN: urn:nbn:de:bvb:12-bsb11148808-2
URL: http://reader.digitale-sammlungen.de/de/fs1/object/display/bsb11148808_00001.html/

Autor: Georg V., Hannover, König, 1819-1878
Erschienen 1860
BSB-Signatur 4 Mus.pr. 45878-3

URN: urn:nbn:de:bvb:12-bsb11149000-0
URL: http://reader.digitale-sammlungen.de/de/fs1/object/display/bsb11149000_00001.html/

Autor: Königsperger, Marianus, 1708-1769
Erschienen 1747
BSB-Signatur 4 Mus.pr. 44470

URN: urn:nbn:de:bvb:12-bsb11148805-6
URL: http://reader.digitale-sammlungen.de/de/fs1/object/display/bsb11148805_00001.html/

Autor: Rathgeber, Valentin, 1682-1750
Erschienen 1727
BSB-Signatur 4 Mus.pr. 44493

URN: urn:nbn:de:bvb:12-bsb11148806-1
URL: http://reader.digitale-sammlungen.de/de/fs1/object/display/bsb11148806_00001.html/

Autor: Stumpf, Johann Christian, 1731-1801
Erschienen 1812
BSB-Signatur 4 Mus.pr. 44733-14

URN: urn:nbn:de:bvb:12-bsb11148812-5
URL: http://reader.digitale-sammlungen.de/de/fs1/object/display/bsb11148812_00001.html/

Autor: Beethoven, Ludwig van [Komponist]
Erschienen [1828]
BSB-Signatur 4 Mus.pr. 2018.6190

URN: urn:nbn:de:bvb:12-bsb11452044-0
URL: http://reader.digitale-sammlungen.de/de/fs1/object/display/bsb11452044_00001.html/

Autor: Beethoven, Ludwig van [Komponist]
Erschienen 1828
BSB-Signatur 4 Mus.pr. 2018.6192

URN: urn:nbn:de:bvb:12-bsb11452046-1
URL: http://reader.digitale-sammlungen.de/de/fs1/object/display/bsb11452046_00001.html/

Autor: Beethoven, Ludwig van [Komponist]
Erschienen [1828]
BSB-Signatur 4 Mus.pr. 88.1084#Beibd.2

URN: urn:nbn:de:bvb:12-bsb11137964-4
URL: http://reader.digitale-sammlungen.de/de/fs1/object/display/bsb11137964_00001.html/

Autor: Küffner, Joseph, 1776-1856
Erschienen 1846
BSB-Signatur 4 Mus.pr. 92.644-14/23

URN: urn:nbn:de:bvb:12-bsb11138730-5
URL: http://reader.digitale-sammlungen.de/de/fs1/object/display/bsb11138730_00001.html/

Autor: Küffner, Joseph, 1776-1856
Erschienen 1847
BSB-Signatur 4 Mus.pr. 92.644-14/23

URN: urn:nbn:de:bvb:12-bsb11138732-6
URL: http://reader.digitale-sammlungen.de/de/fs1/object/display/bsb11138732_00001.html/

Autor: Georg V., Hannover, König, 1819-1878
Erschienen 1860
BSB-Signatur 4 Mus.pr. 45878-1

URN: urn:nbn:de:bvb:12-bsb11148998-8
URL: http://reader.digitale-sammlungen.de/de/fs1/object/display/bsb11148998_00001.html/

Autor: Call, Leonhard von, 1767-1815
Erschienen 1810
BSB-Signatur 4 Mus.pr. 2011.2792

URN: urn:nbn:de:bvb:12-bsb11142493-8
URL: http://reader.digitale-sammlungen.de/de/fs1/object/display/bsb11142493_00001.html/

Autor: Bordogni, Marco, 1789-1856
Erschienen 1848
BSB-Signatur 4 Mus.pr. 2012.4811#Beibd.1

URN: urn:nbn:de:bvb:12-bsb11144149-7
URL: http://reader.digitale-sammlungen.de/de/fs1/object/display/bsb11144149_00001.html/

[U.S.A.] : Columbia Tri-Star Home Entertainment, [2003]

[U.K.] : Universal Pictures Home Entertainment, [2019]

[U.K.] : Universal Home Entertainment, [2018]

[Italy] : Surf Video, [2012]

[France] : Doriane Films, [1996]

[U.S.A.] : Image Entertainment, [1999]

[U.S.A.] : Synergy Entertainment, [2007]

[France] : Pathé, [2005]

[South Korea] : YDM DVDVideo, [2006]

[U.K.] : Artifical Eye, [2014]

Burrows, Terry, author

Creasey, D. J. (David J.), author

Liminal Drifter

Liminal Drifter

Coupe, Stuart, 1956- author

Westerner

Hexel, Vasco, 1980- author

Lutterbie, John Harry, 1948- author

Guernica author Marina Sonkina was recently featured on the cover of BC BookLook! In an article entitled “’Face’ mystery unveils ugly poperty values”, Marina Sonkina’s newest collection, Expulsion & Other Stories, is described as “nothing short of brilliant”. The article begins by explaining, “two thirds of Expulsion consists of Chekovian tales of survival set in […]

Congratulations to David Huebert, the winner of this year’s CBC Short Story Prize! David won this year’s short story competition with a story entitled “Enigma”, which is about a woman who must end the life of her beloved horse. As he explains in a recent article by David Burke, the idea for the story came […]

Dr. Norman Cornett was recently interviewed by RadioVM about his experience translating Farida by Naïm Kattan. In the interview, Norman discusses the significance of Naïm Kattan in general, and his work Farida in particular. Farida tells the story of a Jewish woman and cabaret singer struggling for survival in pre-World War II Iraq. It is […]

In a recent interview with Jeffrey Mackie, translator and scholar Norman Cornett discusses various aspects of translating Naïm Kattan’s Farida. The interview can be listened to below. Norman Cornett begins by briefly describing the basis of the novel, which is “set on the cusp of World War II” and focuses on a Jewish songstress in […]

Subscriber Notice

You are receiving this notice because you subscribe to NewsNet or one of our other email or RSS bulletins. Beginning tomorrow, your subscription will be migrated to a separate U.S. Copyright Office account. You will receive another bulletin after your subscription has been migrated.

You do not need to take any action, but please be aware that if you wish to change or cancel your subscription, you will do so through this page. If you subscribe to other newsletters from the Library of Congress, you can continue to manage those subscriptions through this page.You may wish to check your spam folder to be sure you are continuing to receive these bulletins.

Thank you for your continued interest in news and information from the U.S. Copyright Office.

Imagine you’re ready to apply for your next job. Like most busy professionals, you probably haven’t updated your résumé or your portfolio since you looked for your current job. 

Now you need to update both, and you can’t remember what work you’ve done over the past few years. (In fact, you can barely remember what you’ve done over the past few months!)

So you scramble to update your résumé with new content. Then you spend all weekend scraping together a new portfolio using screenshots of whatever work evidence you can find on your laptop. You submit the résumé and portfolio with your application, hoping you didn’t forget to include any major career milestones you achieved over the last few years. 

This is the process most of us use to approach our job search. We wait until we’re ready to find a job, panic at our lack of résumé and portfolio, and pull together a “good enough” version of each for the job application. (Trust me, I’ve done this many times myself.)

This is a stressful and ineffective way to approach a job search. There’s a much better approach you can take—and you can start working on it now, even if you’re not on the job market.

The Career Management Document

A Career Management Document (CMD) is a comprehensive collection of your résumé and portfolio content. It’s a document you update regularly, over time, with all the work you’ve done. 

When you’re ready to apply for your next job, you’ll have all the résumé and portfolio pieces available in your CMD. All you need to do is assemble those pieces into résumé and portfolio documents, then send the documents off with your job application.

I update my CMD about once a week. I start by reviewing evidence of my recent work. I review Slack messages, Basecamp posts, emails, and any other current work-related content. I write my accomplishments in the format of résumé bullets, using the framework of responsibilities and accomplishments from this Manager Tools podcast. Then I add those bullets to the CMD. 

Here are some examples from my CMD:

• Coached a student on writing a stronger portfolio story to showcase their advanced UX skills, resulting in the student getting a job interview.
• Facilitated an end-of-study analysis in under 90 minutes to help the team synthesize user research data from 12 participants.
• Led a remote retrospective with teams in two offices, developed actionable takeaways, and ended on time despite a delayed start.

My CMD has several hundred résumé bullets, and it continues to grow. I organize content by year and by project. Within each project are responsibilities and accomplishments.

I add any content to the CMD that might go into my résumé someday. I include everything I can think of, even if it seems insignificant or trivial at the time. 

For example, I sometimes help with social media marketing at Center Centre, the UX design school where I’m a faculty member. I include it in my CMD. I don’t plan to pursue social media marketing as a career, but it may be relevant to a future job. Who knows—I may apply to work for an organization that makes social media marketing software someday. In that case, my social media experience could be relevant.

Include portfolio artifacts with your CMD

In addition to capturing bullets for my résumé, I capture content for my portfolio. Each week, I gather screenshots of my work, photos of me working with the team, and any other artifacts I can find. I store them in an organized system I can reference later. 

I also take brief notes about the work I did and store them with the artifacts. That way, if I look back at these materials a year from now, I’ll have notes about what I did during the project, reminding me of the details.

For example, after I facilitated a user research analysis session late last year, I captured evidence of it for my portfolio. I included photos of the whiteboard where I recorded public notes during the session. I also captured brief notes about who attended the session, the date, and when it took place during the project. 

You can use whatever tools you’d like to gather evidence of your work. I use Google Docs for the résumé portion of my CMD. I use Dropbox to store my portfolio artifacts. I create Dropbox folders with dates and project names that correspond to the contents of my CMD.

The key is to collect the evidence regularly and store it in an accessible, organized way that works for you. To know if you’re storing work evidence effectively, ask yourself, “Will I understand this CMD content a year from now based on how I’m capturing and storing it today?” If the answer is “yes,” you’re in good shape.

Update your CMD regularly

For the CMD to work when you need it, it needs to be comprehensive and up-to-date. As I mentioned before, I update my CMD once a week. I schedule thirty minutes on my calendar each week so I remember to do it. 

Sometimes I have a busy week, and I can’t spend thirty minutes on my CMD. So I spend whatever amount of time I have. Some weeks, I only spend ten minutes. Ten minutes per week is better than zero minutes per week. 

Occasionally, I don’t get a chance to update it because my week is so hectic. That’s OK because I’ll probably get to it the following week. 

I recommend updating your CMD once a week and not once a month or once a quarter. If you wait even a month, you’ll have trouble remembering what you did three and a half weeks ago. Even worse, if you schedule a CMD update once a month and then miss it, you won’t get to it until the next month. That means you have to think back and remember two months of work, which is hard to do. 

Updating your CMD every week, while the work is fresh in your mind, gets the best results.

The CMD benefits you in additional ways

The CMD can help you prepare for your job search beyond your résumé and your portfolio. 

You can use it to prepare for a job interview. Since you’re capturing work evidence from each stage of the process in your CMD, you can use that evidence to remember what you did throughout a project. Then, you can craft a story about your role on that project. 

Hiring managers love to hear stories about your work during job interviews. For instance, if you’re a designer, they want to know the journey you took during your design process, from the start of a project to the end. A detailed CMD will help you remember this process so you can share it in an interview. 

I’ve even used my CMD to write blog posts. I’ve been blogging regularly for the past two years, and I often refer to my CMD to remember work experience I had that’s relevant to what I’m writing. When I wrote the article “How to Tell Compelling Stories During a UX Job Interview,” I used my CMD to remember interview preparation exercises I did with students. 

The CMD can also help you track work accomplishments for your quarterly or annual performance reviews. Additionally, you can use it to write job ads when hiring for related roles on your team.

Lastly, I find it rewarding to peruse my CMD now and then, especially when I look back at work I did over a year ago. The CMD serves as a record of all my professional accomplishments. This record helps me appreciate my professional growth because I see how far my skills have come over time.

Learn more about the CMD from Manager Tools

At Center Centre, we originally learned about the Career Management Document through the Manager Tools podcast series.

Manager Tools’ podcasts explain how to use a CMD for your résumé. We expanded their approach to include portfolio work as well. I recommend listening to their podcasts about creating and maintaining your CMD:

• Systematic Career Documentation (Part 1)
• Systematic Career Documentation (Part 2)

Prepare for your next job search now

We tell our students at Center Centre that preparing for your next job search is a process that starts early. It’s like saving for retirement—the sooner you start saving money, the more likely you are to be prepared when the time comes. 

Similarly, collecting résumé and portfolio content ahead of time will prepare you to find your next job whenever you’re ready to do so. It also prepares you for a sudden job termination like an unexpected layoff. If you lose your job without warning, you’ll likely be under a lot of stress to find a new position. Having a CMD ready will relieve the additional stress of building a résumé and portfolio from scratch. 

If you don’t have a CMD yet, now is a great time to start one. Schedule 30 minutes this week to begin crafting your repository of work accomplishments. You’ll be glad you did when you seek your next job.