CODI News

Volume 12, Number 3: Summer 1998

Menu – Master (MAST)

President’s Letter

WHAT IS A CODI?

What is "a CODI"? That was the email subject of a note I received from Bob Fish during ALA. He inquired to know what CODI could do to help his site with a problem he’d been having. Flying to Washington, DC for ALA, I wondered, "Am I a CODI? What defines a CODI?"

What is "a CODI" to you? Someone who lives and breathes Dynix menu mnemonics? Someone who recites recall in their sleep? Someone who answers a question when support has suggested there is no answer? Someone who wears a face and appears in flesh and blood once a year at a conference?

There were about 40 other "CODI"s who attended our informational meeting at ALA: Directors, SAs, and others interested in keeping their systems running. People concerned about the product direction at ALS. People concerned about budgets and deadlines, new technology and survival, and just plain worried about getting through another year with not enough staff and way too many projects on their plates.

This summer, the CODI Board began preliminary discussions with two groups: CANDU Board members, and Horizon Board members. Some of our discussions will lead us to define who we are in terms of our own organizational Bylaws. Other discussions are a response to our own concerns of product vision in a global world. I will be visiting with Board members from DUG and CODA in the next several weeks to inquire about how we, as separate user groups, can further work together to strengthen our resources and cooperation.

Does geographical boundary define our CODIness? If so, what is our commitment to our regional kindred, the library down the street or across the state? What is our commitment to our global kindred? What is the value of "a CODI" among us? And, what is the value of "a CODI" to our vendor of choice, ALS?

The identity of "a CODI" may require adjustment as we move toward a more graphical product line. The identity of CODI as an independent user group representing the needs and concerns of customers holding the software licenses to ALS products in the US may also change over the next several years. It may affect our programs, our membership dues, our ability to sustain or produce conferences and programs for our membership. We are, in fact, part of a living, moving, breathing federation of many states, if I may quote Brian Hackett, of the University of Huddersfield. How we choose to participate with fellow users, and with fellow kindred user groups, will reflect our identity and the very essence of what it means to "be a CODI".

The cooperation and strength of our network of users, from region to region, from state to state, from continent to continent, is what enables us to reach the ocean, so to speak. What does the ocean symbolize? Well, for many of our international colleagues, the ocean has sometimes symbolized a division, an obstacle, a large source of isolation from the US clients and US products we all share.

Coming from a land-locked mass called Kansas, I have always thought of the ocean as opportunity. Granted, I am always dependent on other contiguous states to reach the ocean, most notably, I depend on the goodwill of the residents of Oklahoma and Texas for safe passage during the two-day car trip to reach the sparkling waters of Padre Island. Perhaps you yourself don’t strive for the ocean. Perhaps *you* endure a two day car drive through Kansas to get to the cool refreshment of the Colorado Rockies. Or perhaps you trust the goodwill of the fine natives of Iowa to guide you through the maze of corn out into the forests and lakes of Minnesota.

It is this very goodwill among states sharing common goals (commerce, highways, tourism) that allows us as individuals to achieve *our* goals: rest and relaxation, meeting new friends, enjoying a change of pace. Whether we seek the ocean, mountains, or forest, we experience freedom, danger, and sheer beauty when we reach them.

The interdependence of neighbor states is rarely given a thought in today’s environment of electronic mail and Internet services. Dynix_l has been a successful demonstration of the boundless information it has shared with all of us. The Australian archives of Dynix_l, cutting across oceans, mountains, and time zones, provides another example of information, support, and great response time that literally knows no bounds.

We work *through* one another and *with* one another to reach our "ocean". Is our "ocean" isolating, or full of promise? Is it fraught with peril, challenge or opportunity? All three, probably. Being "a CODI" has never been something most of us take lightly. We are instead passionate, well-informed, even well intentioned users that try our best to keep our systems running.

Are you up to the challenge? Are you "a CODI?" I hope so, or else you probably wouldn’t be reading this. Do you know someone that should be "a CODI"? Can we count on you to share the excitement with a colleague or nearby site?

Rough seas or smooth sailing, you *are* "a CODI"! Happy Travels!

There have been several postings recently concerning the current state of customer input into the enhancement of the traditional Dynix software and the also the role of customer input into the development of new Ameritech Library software. Also people have been asking about the status of the old CODI-ED database which we used for a number of years for listing enhancement ideas. Here is an attempt to answer those questions:

The old enhancement process has been replaced by the new JAD process, which is designed to take an active role in the development of the new Ameritech software as well as the enhancement of some parts of the traditional Dynix software. It has become evident that rather than put more energies into the traditional text based Dynix software, that Ameritech was following the trend to graphical products. This meant that rather than spend a lot of time in enhancing the Dynix software the company was interested in working with the customers as they developed the next generation of products. This also came at a time when the enhancement committee structure appeared to have ceased to function satisfactorily. The new JAD (Joint Application Development) process has been designed to provide a framework for the customers and Ameritech to work together on the development of new software. For details concerning the structure of JAD, please see either the CODI or Ameritech Library Services WEB pages. Three projects have been implemented under JAD: Telecirc II, technical services workstation, and bindery. Telecirc II is just about ready for general release. The technical services workstation group is examining functionality needs and looking at prototypes. Bindery is an add on to the traditional Dynix software and this group is looking at functional requirements.

The CODI-ED database is virtually shut down. I have printed off all of the existing ideas and I am in the process of reviewing these for content, accuracy, and whether or not they are already in the software. I am also categorizing the ideas so that like ideas can be considered together. As of this time the serials experts at Ameritech have reviewed the ideas that dealt with serials. I have some comments from them about the ideas. This is all in preparation for a new list that will be made available as a part of the Ameritech WEB site. The new list, which is carrying the working title of "bright ideas," will include valid ideas that were submitted to CODI-ED. I met with Ameritech staff last month to discuss the design of this addition to the WEB page and work is progressing on this. Other projects at Ameritech require urgent attention so this new list will not be available for some time.

This report is primarily to answer the question of "how do I submit enhancements?" Currently, there is not a list or a way to submit ideas. The thing to do is to keep your own list of ideas and then when a JAD project is announced that covers that area, you can volunteer to take part. Or when the "bright ideas" WEB site is available you can submit the ideas then.

NEW DIRECTIONS - Y2K AND BEYOND is the 1999 CODI conference theme! As CODI members, we embark upon this year's conference anticipating what is ahead in the realm of technology and wondering what kind of evolutionary process our library's IT departments will too soon experience. Seattle, even in February, can be an exciting place to visit and meet technology leaders who are forging ahead into the Y2K future. Yes, this is Bill Gates, Paul Allen, and Boeing country! Unfortunately, they will not be joining us in person but their influence will permeate our ranks. Therefore, the conference planners are hard at work developing a conference program that will generate new ideas, new energy, and confirmation of who we are and what we do.

For the early arrivals on the afternoon of Tuesday, February 9th, the Local Arrangements Committee has scheduled a bus tour to showcase four libraries in the Puget Sound region. During this tour, we plan to visit Microsoft Library and Museum, Boeing Library, Bellevue Regional Library of the King County Library System and a Seattle Public Library site.

Advanced preliminary program highlights feature presentations on Y2K, Virtual Library, electronic books, Horizon sites that have migrated from DYNIX, PC Managed solutions, new Cataloging and ILL applications and networking.

We are off to a good start but we know we have a lot of work to complete. If you are interested in working on this year's conference, please contact Susanne Woodford, CODI Conference Chair, King County Library System at 206-684-6632 or email me at susannew@kcls.org. I am still seeking a volunteer who would like to chair the New Members committee. Remember the fun is just beginning!

You can submit your program idea by using the web form found at this address: http://www.carr.org/codi.

This web site, hosted by Scott Reinhart, Carroll County Library System, will also post the conference registration form and is linked to other conference sites and the official CODI web page. A preliminary conference schedule and registration form will be sent to the membership by October 15, 1999. Advanced registrations will be accepted until November 30, 1999.

For suggestions or questions on the conference programming, please contact Pat Burke, Prince William Public Library System, 13083 Chinn Park Drive, Prince William, VA 22192-5073, 703-792-4866 or email her at pburke@pwcgov.org.

Patricia Burke, Program Chair, Prince William County Library, VA

Debbie Hickman, Exhibits Chair, Shawanee Library System, IL

Layne Nordgren, Media/Internet Chair, Pacific Lutheran University, WA

Meredith Wagner, Jefferson County Rural Library, WA, Local Arrangements Co-Chair

Charles Coldwell, Seattle Public Library, WA, Local Arrangements Co-Chair

Marganne Weathers, Fort Lewis Library System, WA, Registration Co-Chair

Linnea Patrick, Port Townsend Library, WA, Registration Co-Chair

Pia Jones, Conference Planner

Frances Orton, Membership Services Coordinator

Susanne Woodford, CODI Conference Chair

King County Library System

300 8th Avenue North

Seattle, WA 98109-5191

206-684-6632

2:00 CDT - Conference Call

Present: Susan Johns, Gretchen Freeman, Thom Hendricks, Ginger Olson, Susanne Woodford, Ann Tenglund, Cathy Schappert

New Board members were welcomed. Everyone had received their position descriptions, and will inform Frances Orton and Bonnie Schuster of any corrections to the Board roster. Johns referred everyone to the CODI By-Laws, and noted that we follow Roberts Rules of Order.

Schappert had no corrections to the report previously faxed to the board. The Salt Lake Conference has one $3,000 outstanding invoice. The Conference did make some money, but since the previous conference was over cost by $14,000 we have had to use much of our reserves. Treasurer’s Report was approved as presented.

Johns previously emailed a monthly meeting schedule to the board. Some rescheduling was discussed. It is important to have a quorum for meetings, since we waste the cost of a conference call if we cannot approve motions. It was explained that ALA meetings are informational, thus board attendance is not required and there is rarely a quorum to conduct business. Partial reimbursement is only provided for the one person (generally the President) who will be conducting the meeting. Board members are definitely encouraged to attend when possible, and informal board discussion is scheduled even if official business cannot be conducted.

Under By-Laws Article 6, Section 3, the board voted to have John Hurley fill the vacant Past President position for this year.

Tenglund summarized the ALA Informational Meeting. She reported on the Web survey, and Gretchen Freeman and Ed Riding gave the ALS update. Many directors and others who did not attend CODI were able to attend this session.

Kate Olsen had started this to provide continuity from one president to the next. ACTION: When we again have a past president next year, this helpful report should be resumed.

Schappert and Johns presented a draft budget. The accountant had recommended some changes to document petty cash expenditures that Frances needs to make, and refunds made for dues that are incorrectly paid. Frances’ new status as an employee will require some changes for the FICA payments. In June the Board approved a one-time expense to upgrade Frances’ computer, which is a desparate need. Adding in areas where expenses will likely go up this year, the draft budget could not be balanced with anticipated revenue. The Board discussed possible ways to reduce costs evaluating printing and postage costs for the newsletter, conducting more board business electronically and less by conference call, etc. Schappert, Tenglund, Freeman, Orton, and Heimburger were appointed to a Newsletter Committee to explore reducing those costs. Raising membership dues has not been done for several years, even though CODI has added initiatives such as international participation. Decision was made to table the discussion at this meeting. ACTION: Johns and Schapppert will present a revised budget proposal in August.

Complete report will be in the Newsletter. There was strong support for joint conferences with Horizon, and also for trying a rustic setting. Ranking of the East Coast and Midwest sites has been given to conference planner, Pia Jones. ACTION: Pia to have site selection report for the Board for the September meeting.

Numerous changes are needed. Biggest issue is how to define CODI membership, since Provo office support is no longer correct. Other issues that need change are items that conflict with current job descriptions, elimination of enhancement committeess, newsletter policies. There was agreement that Article VI, Section 5b should read "conference chair." ACTION: Board should continue to think about issues, and item will be placed on another agenda.

ACTION: Table for now. Discuss electronically.

ACTION: Table for now.

Hendricks, Regional Liaison, has received information from Jerry Kuntz, predecessor. ACTION: He will contact regional groups to determine updates needed for the Web site. Olson, JAD Liaison, has not yet connected with Marge Freeman, JAD Coordinator. Freeman will be submitting a CANDU report to the Board. Moving CODI-ED to the to-be-developed "bright ideas" database is being organized.

Conference report has been mailed to the Board. There were no specific questions.

Johns explained the standing Conference Committee that was designed to provide guidance and support for the Conference Chair. The committee consists of the exectuvie board and one member at large, plus the Membership Services Coordinator, the ALS Liaison, and the Conference Planner. Thom Hendricks was elected the member at large representative for this year.

ALS has asked that Dynix and Horizon seriously consider a joint conference by 2000. The CODI membership survey definitely expressed interest in this, and Johns has been in contact with Horizon officers. Despite the interest, there are many issues that need to be resolved, and both groups are currently very close to independent site selection for that year. Areas of concern that need to be addressed included: We have different conference pricing structures. We each have different conference planners. We have different reimbursement structures. Their fiscal year is Jan-Dec, ours is July-June. Converting will mean either two conferences in one year, or no conference one year, for one group. Horizon meets in the East in 1999, we meet in the West in 1999. Each group is currently planning to go the opposite direction in 2000.

ACTION: Board will continue discussion electronically, and also discuss who might represent CODI at the Horizon meeting this year, November 9-11, in Raleigh Durham.

Johns discussed ALS telephone system with Roy Willard.

ACTION: Johns will be sending letter to CANDU and will copy CODI Board.

CODI archives from Winslow have been given to Frances.

ACTION: Schappert will get Winslow address (she has retired) so we can send a thank you.

Schappert recommended the newsletter cost analysis be reassigned from the Treasurer to the newly formed Newsletter Committee.

JAD Coordinator still lacks position description and title. Let Marge know of any creative ideas. ACTION: Title and duties need to be developed for JAD Coordinator.

August 19, 1998

Back to the Master Menu (top of this file)

schuster@selway.umt.edu

C O D I

Back to the Master Menu (top of this file)

C O D I

Back to the Master Menu (top of this file)

Back to the Master Menu (top of this file)

Ann Tenglund passes along this reminder. "Please bookmark www.sbu.edu/codi This is where you’ll find a link to all CODI material, as well as information about Dynix_L. No need to remember all the separate addresses—this one address gets you where you need to go!"

brh@richland.lib.sc.us

Back to the CODI Web page