The Ohio State University

Google Calendar

For what we use Google Calendar?

A section supervisor can view simutaneously all work schedules of employees in the form of shared calendars.

Requirement

Both suppervisor and employees must have a Google account and use Google Calendar. Note, you don’t have to have a Gmail address in order to open a Google account. You can use whatever email account you have been using to open a Google account.

How to have someone share his/her calendar with you?

• When someone starts Google Calendar, he or she gets a default personal calendar. One can decide to use this default personal calendar for sharing; or, to create a new calendar for the purpose of work-schedule, and share ONLY this new calendar with his/her supervisor.
• Note, if one decides to share ONLY the work-schedule calendar, make sure the default personal calendar is NOT shared from the beginning. Then, he should create a new calendar and add person (email address) to share.
• Make sure the email address (of the person one wants to share calendar with) is the one that he or she uses to sign in Google account.

to be continued…

Add comment

100 and 700 on a bib record are for names of responsibilities. 100 is for main author; 700(s) are for secondary authors.

• Use the Authority form (or established form) in the 100 and 700. But transcribe the name according to piece in 245.
• If there is 100 field, then the 1st indicator of 245 is 1; If there’s no 100 field, then, it is 0.

700 (see above)

245 is for “title and statement of responsibilities.”

• For, our microform project, you will always have a $h [microform]
• Pay attention to the 1st indicator (see under 100); the 2nd indicator is for “non-filing characters” and for us, it is usually 0.
• Study Varieties in titles and statement of responsibilities.
• About “sub title”. Use $b for sub title. It can be either before or after the $h, depends.
• Study Title proper and varying form of title.

246
250
260
300
490 and 830 combination
533
500
9xx fields

Add comment

Fixed fields

• Desc: a (Cataloging Rule – “a” means Anglo-American Cataloging Rules)

• Elvl (Cataloging level): use “I” for full level; use “K” when lower level (when you are not very confident for some info provided in the record)
• Srce: d
• Form: b (”Form.” means format, and “b” indicates microform)
• Ills: co-related with the 300 field.
  When 300 b subfield has ill. (illustrations), you will have a; when it has maps, you have b; when it has port. (potrait), you will have c in the Ills boxes.
• DtSt: put “s” (single date), “m” (multiple dates).
• Dates: published year(s). If “m”, put beginning year in the 1st box, ending year in the 2nd.

Add comment

Avoid creating “hybrid records” by revising the master record with different language-based data elements

One of typical cases is that N5L (=National Library of China) original MARC records having 040 $b “chi” which should mean that the record represents the Chinese language “cataloged” bibliographic record. These records usually contain the 300 field with Chinese script data, and may also contain 500 note fields with Chinese script data. These master records should not be changed into the English-language cataloged record by editing the 300 field and 500 note fields with English texts.

DO NOT revise the record, instead, please create a new English-language cataloged version of the record. The Chinese version record and the English-version record for the same bibliographic entity are not considered duplicate records but they are parallel records to each other. The 040 $b coding such as “chi” or “eng” is for the language of cataloging of that record.

For details, read Ms Hisako Kotaka, OCLC message posted on CEAL list serve.

Add comment

Cataloging Department Workshop: New Tools for Cataloging and Communication
Room 754, Ackerman Tech Center
January 28 Thursday 10 AM to 12 PM

In this workshop, we are going to introduce some new tools for cataloging and task management. We have tried these tools in our Non-Roman Cataloging Section, and found that they are very helpful and easy to use. Therefore, we would like to share our experiences, and hope all of you can explore and try them out, and see if they can help your works.

The new tools we tried include some Web 2.0 applications such as blog, online realtime documentation and wiki, and e-learning tutorials. Today’s focus is on using a blog.

The Cataloging Department Blog

The word blog is a short term coined for Web log. A Web log is a journal kept on the Web, but it can do much more than a log book. A blog is a strong online social networking tool.

A blog can be for personal or for the use of a group or a corporate body. It can have a single or multiple authors (or contributors).

Probably the most beneficial features of using a blog for management is the ease of updating! In Web 2.0 language, we call the old websites static. For examples, if we want to update our Cataloging’s homepage, we have to first create html files, and then hand to and wait for the Webmasters to put the files onto the website. By the time the documents being put on the web, days have passed… But to update a blog? It’s on our fingertips — log in, write, and post. It’s there. Also, we can easily change the nevigation or layout of the blog; integrate online tools, documents, and all useful resources on the blog.

We have opened a blog for the department on the library’s blogs site. The department blog will be enaged to enhance communication between sections and co-workers within the department and with other units in the library. Everyone can use it and is encouraged to contribute. Now, let us use the real cataloging department blog to explore some blog features.

• Access to the blog
  The blog is listed on the Library blogs page:

Go to the library homepage

Click on Library Blogs

and select Cataloging Department

• The layout (or, “presentation” as it is called by the blog product we’re using)
  The Cataloging blog still looks very imature now, because it’s waiting for us to build it up together. Probably the first thing we want to do is to decide which layout form we like. Well, rightnow, we don’t have much choice. There are only two forms we can use. One is this, somewhate (I think) plain looking one; the other is what I’m using for the Non-Roman Cataloging Section and it looks like this. It is, however, relatively easy to make changes, and the result is instant! [demonstrate how to change the layout]
• Features and creativities

Posts

Pages (documentation)

Categories

The Search box

chronology vs. categories vs. priorities

Publicity and control: locked posts and pages for internal use

• Making contribution to and managing the blog: the Admin Panel
  The blog is like OSCAR or OPAC, and the Admin Panel is like Connexion or Millennium…

Log in

write a post

apply category or categories

write a documentation or “page”

edit a post or document

• Other features

Understanding “blogroll”

How to become an author or contributor?
As said, everyone at Cataloging can use and is encouraged to contribute to the blog. There are basically 4 types of role assigned to users of a blog:

• Subscriber: someone who subscribs to read the blog, but can’t edit it.
• Contributor: someone who can write and manage their posts but not publish posts.
• Author: someone who can publish and manage their own posts.
• Administrator

To become an author or contributor, you need to first register. To do so, go to the blog and scroll down to the Admin Panel area

• Click on Register.
• Follow the steps to register.
• You will receive a email, and you need to follow up the instruction provided in the email message to complete your registration.
• Once you are registered, the administrator of the blog can then add you as an author or contributor

* Probably at the beginning, each section can select one or two author/contributor-in-chief, so not everyone has to be registered.

Limitation of blog

This ends the first workshop of New Tools for Cataloging and Communication.

Add comment

The following are special instructions for dealing with non-contemporary Japanese author names appeared in our JMSTC microfiche collection. Click here for general procedures of JMSTC cataloging project.

1. First, try to search for a Name Authority record (on Connexion), and see if there is an authority file established for this author.
2. If there is an authority file, use that for the name in 100 or 700 fields in the bib record. Note, the authority form can be different from that in the 245 statement of responsibility.
3. If there is no authority file established for the name, we should try to keep consistant for the author name — at least in all records created by us. Check OSCAR for form(s) beinig used in our library catalog.
4. This means, we should keep using a consistant form of that author, and if there’s a year associated with that author, include that on the bib record. The form can be the “real” name or the author’s psedonym.

For examples,
稲岡奴之助 (Inaoka Nunosuke) often appears in different forms, sometimes it is 奴之助, sometimes 稲岡奴之助. Upon a time, we discovered the author’s birth year (1873) — from reliable and reasonable sources, from that point, we need to establish a form of the author’s name (i.e. that to be used for 100 or 700 on the bib record). For this case, it should be
┌稲岡奴之助, ǂd b. 1873
└Inaoka, Nunosuke, ǂd b. 1873

呑気楼三昧(Nonki Ōzanmi) is the psedonym of 高松豊治郎 (Takamatsu Toyojirō)

This is an example that an author has an authority file
松林伯圓, ǂd 1832-1905
Shōrin, Hakuen, ǂd 1832-1905.

Add comment

This post explains Call number suffix in contrast with Volume identifiers

Usually a call number ends with the year of publication, but OSUL has a local practice of adding something called “Call number sufix” to assist retrieval of items in special format. Note (1) the call number suffix is added to call number on the bib record; (2) only established sufix can be used, and these are:

1. Computer file [If GMD is “electronic resource”] Example, PL687.A3 Z4 1999 Computer file
2. DVD [If GMD is “videorecording”] Examples,
3. Videotape [If GMD is “videorecording and in VHS format] Example, PN1997.C485 1996 Videotape
4. Phonotape cassette [If GMD is “sound recording”] Example,
5. Kit [If GMD is “kit”] Example, DP102.I853 2001 Kit

A volume identifier, on the other hand, is something to be added in the Item record — check here for a full explanation on Volume Identifiers.

When such a suffix has been added as part of the Call number in a bib record, there will be no necessary to add volume identifier for each item in that format (but any supplements still need volume identifiers). Examples,

• Zenkoku hogen shiryo [electronic resource] (1999) has total 13 items, v.1 to v.12 CD-ROMs (computer files) with a booklet.
• Oshin [videorecording] (2003) is a set of DVDs in 7 volumes, each volume contains 4 to 5 pieces of DVDs.
• Spoken Swedish [sound recording] is a 5-volume set of phonotape cassette accompanied with a book. So the call number is PD5113.F72 1990 Phonotape cassette.

For details on treatment of special formats, check Special Formats Requirement.

Add comment

(Also see documents “Bound-with processing for monograph” and “Bound-with: Special Collections” under CAT documents)

If two or more different works are bound together, either as one part (single volume) or as separate parts but bound together in a case; and no collective title* is made for these works (often the title of the first work appeared as the title), we can treat them as “bound with” and provide a “with” note as defined by AACR2.

• Create separate bibliographic records for each work/title.
• Assign one classification to all works; if different, classify under the first title.
• Add a 501 field (501__ with xxx) in each bib record.
• Create only one item record under the first title.
• Link that item record to other Bib records.

The result of this is: When a user searches either title, he/she will get the bib record made for that title, and see an item available under it. When the user checks out the item, he/she is actually checking out all the works/titles bound together at the same time. In other words, when one title is checked out, the other are also checked out.

*Do not use the “bound-with” treatment for different titles that are grouped under a collective title.

2 comments

Field 440 (Series Statement/Added Entry–Title) has been made obsolete in the MARC 21 Bibliographic Format in Fall 2008. For details, see MARBI’s Proposal.

Current Practice

• Use a combination of 490 and 830 to trace the series title.
• The 1st indicator of 490 is redefined. Now, using 1 means “series traced in 8XX field.”
• Put the traced form of series title in the 830 field.
• Note 490 does NOT have p or n subfields, but v or x subfields can be used.
• When there are additional series titles (e.g. parallel title in different language), add 830 field for each.

Examples.
A Korean series title
OCLC #123909673

┌490 1_ 奎章閣資料叢書. 藝術篇 ; ǂv 2
└490 1_ Kyujanggak charyo chʻongsŏ. Yesul pʻyŏn ; ǂv 2
┌830 _0 奎章閣資料叢書. ǂp 藝術篇 ; ǂv 2
└830 _0 Kyujanggak charyo chʻongsŏ. ǂp Yesul pʻyŏn ; ǂv 2

Examples for additional series title:

OCLC #416156980
OSCAR b65341703

┌490 1_ 《中华文明史话》中英文双语丛书 = ǂa History of Chinese civilization
└490 1_ “Zhonghua wen ming shi hua” Zhong Ying wen shuang yu cong shu = ǂa History of Chinese civilization
┌830 _0 《中华文明史话》中英文双语丛书
└830 _0 “Zhonghua wen ming shi hua” Zhong Ying wen shuang yu cong shu
- 830 _0 History of Chinese civilization

OCLC #318646126

┌245 00 哄笑十八番|h[microform] : 英文 …
└245 00 Kōshō jūhachiban [microform] : eibun ….
- 490 1_ The “rising generation” series ; ǂv 1
┌490 1_ 明治期刊行物集成 (JMSTC). 第1期, 文学, 言語編 ; ǂv 07951
└490 1_ Meijiki kankōbutsu shūsei (JMSTC). Dai 1-ki, Bungaku, gengo hen ; ǂv 07951
- 830 _0 “Rising generation” series ; ǂv 1
┌830 _0 明治期刊行物集成 (JMSTC). ǂn 第1期, ǂp 文学, 言語編 ; ǂv 07951
└830 _0 Meijiki kankōbutsu shūsei (JMSTC). ǂn Dai 1-ki, ǂp Bungaku, gengo hen ; ǂv 07951

Note. If the title originally has articles, such as “the”, keep it in the 490 field, but do not enter it in the 830 field. OCLC Bib Formats & standards has made a note for this: “Current practice is to enter the title without articles and use 2nd indicator value 0.”

1 comment

Current cataloging rule (RDA):

• “A date associated with the person is required when needed to distinguish a person from another person with the same name.” — RDA Section 3, chpt 9.3
• “Take information on dates associated with the person from any source.” — 9.3.1.2 Sources of Information
• “Record dates in terms of the calendar preferred by the agency creating the data. Record a date associated with a person by giving the year alone.” — 9.3.1.3 Recording Dates Associated with Persons

There are three types of date associated with the person which are “required when needed to distinguish a person from another person with the same name.”

• Date of Birth
• Date of Death
• Period of Activity

[Common practice] Optionally, add date(s) to any personal name, even if there is no need to distinguish between headings. — AACR2 22.17A

PROBLEMS

1. When the person’s LC authority form does not have a date, but our sources present a date or dates

– Suggested treatment: Give the date(s) in the vernacular field, and leave the romanization field as given by LC name authority record.

┌100 1_ 雑賀柳香, $d 1857-1902
└100 1_ Saiga, Ryūkō

2. When there is no LC authority record eastablished for a person name

***Thumb-up rule: Be consistent ourselves.

When there is no LC authority record, check OSCAR to see if we already have records of the same person.
If found, follow the way we did on OSCAR.

Note sometimes you find information given by other sources such as Wasada, Keio, 国会図書館 (NDL), etc. For examples, a Wasada record has

┌700 1_ 花笠文京, ǂd 2代目 1857-1926.
└700 1_ Hanagasa, Bunkyō, ǂd 2 1857-1926.
┌700 1_ 歌川国政, ǂd 3世 1848-1920.
└700 1_ Utagawa, Kunimasa, ǂd 3 1848-1920.

Only take reference, but follow the way we did on OSCAR, i.e.

┌700 1_ 花笠文京, ǂd 1857-1926
└700 1_ Hanagasa, Bunkyō, ǂd 1857-1926
┌700 1_ 歌川国政, ǂd 1848-1920.
└700 1_ Utagawa, Kunimasa, ǂd 1848-1920.

Instructions on recording dates of birth for two or more persons with the same name born in the same year.
9.3.2.3

Add comment