Master To Do List
961212
(revised constantly)
961212
(revised constantly)
A. Patron Things
A1. Enrolled: Priority: 4
Our recommendation to the Council says "currently enrolled". What
about intersessions? Short ones such as spring break versus long
ones such as between summer and fall sessions? What about institutions
who give local borrowing privileges to their own
students during summer (if they were enrolled spring term)...... if the
patron's local record isn't expired and if there are no other blocks, the
system will allow AB for that patron. We should talk about and make some
recommendations about this.
Schedule: via e-mail or at November 8th ABC meeting
Update: Accidentally talked about it at 961007 meeting and crafted a request for Council clarification a little later. It's become a priority 4 issue, for now.
Update: Recommendation to Council approved by OBC. Council to Discuss.
Update: 961115: Recommendation adopted by Council.
A2. Patron
verification: Priority: 1
Each institution will need to tell us what field they use for patron
verification (univ ID or barcode) and whether they currently use a PIN
in "View your own record".
Schedule: via e-mail or at October 7th ABC meeting.
Update: Each institution can choose their own field to use for patron verification. 10 of 12 Orbis libraries currently use patron verification and therefore have already chosen their field. The other two have indicated a field to use. Table for III Completed.
A3. Penalty points: Priority: 2
If we discover that we can use penalty points for Orbis alone (I.D.),
discuss and make recommendation to Council. If it's possible, would
we want to assign penalty points to patrons who don't pick up Orbis
books? Need to know if any Orbis Libs currently use penalty points.
Schedule for discussion: at a November ABC meeting, or via e-mail before
ANSWER: No Orbis-only penalty points at present. (From Sandy/Anne on
960925)
A4. Orbis PTypes: Priority: 1
Need to agree on the Orbis Ptypes for the 2xx range.
Schedule for discussion: at Oct. 7 ABC meeting, or via e-mail before
Update: We added 205: Remote Borrower. This Orbis Ptype will be used for remote borrowers needing Orbis privilges in Orbis libraries in institutions with which they are not affiliated. (On-site reciprocal borrower local PTypes will be mapped to this 205 Orbis Ptype.) Table for III filled out.
Update:961026: Council didn't really talk about this specifically, but since they reaffirmed their earlier decision about who gets borrowing privileges, I'm gonna close this one. I don't think they want to get to this level of detail, as long as we implement their policy decisions. SStevens.
A5. Orbis PTypes : Priority: 2
Shirien and Nancy will create an Orbis PType chart based on Council-approved categories of patron access. Then each institution creates a mapping table which shows every local patron type mapping to the appropriate Orbis patron type. This should not be done in the local system, but in a word processor, and sent to Shirien and Nancy for review. Then it is returned to the local site for entering into the Ptype table.
Schedule: Shirien and Nancy to create Orbis PType chart, and Shirien will send ABC request for conversion table via e-mail. Shirien and Nancy will review tables and bring questions, etc. to ABC meeting October 7.
Update: Got discussed and done. Orbis PType Table created, now waiting on local conversion tables which are due October 18th or 23rd.
A6. Local PTypes: Priority: 2
Need to be sure all local PTypes are not in the 2xx range. This will be covered in October's workshop and subsequent ABC meeting. After Patron workshop, local lib's need to review own local Ptypes and move any that are currently in the >2xx range to <2xx.
This is now each local institution's responsibility.
A7. System Blocks: Priority: 1
For 2xx PTypes, discuss:
--loan periods exceed exp. date?
--max $ owed?
--highest level OD reached?
--max items at any one time?
--max # holds at any one time?
Schedule: for discussion at Oct 7 ABC meeting, and recommendation to Council.
Update: Shirien to fill out the Orbis Patron System Block Table with something that seems relatively reasonable, and will send the block table to reps via e-mail for discussion and vote. This table due to III at end of October.
Update: Turns out that the only field in the Orbis patron block table that the system checks the the max items field. ABC making a recommendation to Council, and then will complete the III table.
Update: Recommendation to Council approved by OBC. Council to Discuss.
Update: 961028: Council approved recommendation.
A8. Manual blocks: Priority: 3
Discuss local blocks used (type and policy about them), and see whether there are any problems. Also been some discussion about whether we want to make an agreement about one institution calling another one and asking that a block be placed, or a recoding be done on particular patrons who loose Orbis items flagrantly. (the patron could be recoded to a local circ only, but this would require a new set of local Ptypes....... just a thought. Might be better than blocking them from their own library.... or maybe we we don't need anything at all. This was suggested as a discussion topic, so we'll approach it when we talk blocks on Priority 3 items.)
Update: 961212:
Seems like this is a minor issue, and how an institution blocks their own
patron's privileges isn't so much a concern of the rest of the group.
Given our real tasks, I'm just going to close this one without asking
Committee permission, and if anybody brings it up, I'll reopen it.
B. Item Things
Orbis B1. ITypes : Priority: 1
After III answers IV.M, each institution creates a mapping table which shows every local item type mapping to the appropriate Orbis item type. This is not done in the local system, but in a word processor, and sent to Shirien and Nancy for review. Then it's sent to the local site for entering into the IType table.
Schedule: by end of October
Update: We changed the label "monograph" to "circulating". If we have other types of items which circulate in the future, and if those circulations have different loan periods or fine rates or other aspects that are different from the current Patron Loan Rule, we can add another 2xx Itype and new 2xx Itype label, and change the "circulating" label of Itype 200 to something else at that time. Orbis IType Table filled out, still need Itype Conversion Table done. Institutions to send table to Shirien by October 18th or 23rd.
Update: January 11, Ann Rakes told us the only circulating Itype is 200. All the rest in the 2xx range are noncirculating. We changed our tables for Itypes, but left Ptypes as they were. (200 = non, 201=undergrad, 202= grad, 203=faculty, 204=staff, 205=Remote Orbis borrowers -- the ones we adopt locally into our own databases).
B2. Items lent: Priority: 2
If we've agreed that all monographs in general collections go out,
have all the monographs in NON general collections either been changed
to a different IType in the local database, or have a "o" in lib use
only status put into their status fields? (This will be covered in the
Patron/Item workshop in October: don't make changes now to your databases.)
Schedule: After the Item workshop on 960107, local libraries will be
responsible for assuring their own coding is appropriate. Nancy
Nathanson
can answer questions as needed. Databases need to have appropriate
coding
by the beginning of the test phase.
Update: IF institutions are going to change their local use of item loc and Ptype: after they make any fixes to their IType charts and globally update any item records to match those Itype fixes, they should be sure they have status "o" codes in those records which have a local Itype that maps to the circulating Orbis IType (201) but which should not be lent via Orbis (example: reference monographs).
ABC has no more work to do on this one: it is up to individual institutions. In whatever way each insitution uses their locs, ptypes, and itypes, they must be sure they can map local ITEM Types (without relying on item locs) to the circ or noncirc Orbis type.
B3. New Books: Priority: 1
Are there any "special" categories of items we should talk about (such as New Books, perhaps) that really are general circulating items to our patrons, but which we may wish did not circulate to all Orbis borrowers? (Note: the general philosophy we've adopted says that if they're generally circulating items, they should go out via Orbis. This question is raised just to be sure we all agree to that and if we have any questions about some smaller collection, this is the time to raise it.)
Schedule: For brief discussion at next ABC meeting, 961007. If there are no problems to solve, don't think we need any recommendation to Council, since already accepted recommendation covers it.
Update: Since nobody treats "new books" any different than they treat other "monographs" in their circulating collections, we didn't have to make any recommendations about this one. They're folded into the general collection.
B4. Automatic Selection: Priority: 1
Anne Rakes says that the only reason there is an option for automatic selection is because the system was originally built without it, and then later when it was added, it was as an option. She nor Sandy could think of any reason why anybody would want manual selection in patron mode. Discuss: Should ABC make recommendation to Council that we opt for automatic selection with the option of manual selection in tech mode.
Schedule: Discussion at next ABC meeting, 961007, and recommendation to Council.
Update: Recommendation to Council approved by OBC. Council to Discuss. Update: 961028: Council approved recommendation, and decision made.
B5. Status codes: Priority 2
All Orbis libs already have a uniform status code table for item records, and have agreed not to put any more codes in on their own. We all will need to add some Orbis status codes to our local tables.
Schedule: We know from III documentation which specific status codes to add to our local status code chart. Nancy or Shirien will send request to each library to add new codes to charts, to be done prior to test phase.
Update: none yet. Doesn't have to be entered into each
institution's status code table until right before test phase.
Later information: we figured that even though each local lib must enter
the same status codes into their tables, and the status codes must have
the same basic meaning, it could be up to locl lib's whether they want to
display any label to the code in their local OPACs, or whether they want
the status code label to be blank. For discussion in more detail see
this
page, or this
one
Update: Recommendation to Council approved by OBC. Council to Discuss.
Update: 961028: Council approved recommendation.
Update: Nancy and/or Shirien will notify libs when it is time to enter these codes into local tables.
B6. Loan periods: Priority: 1
Need to make recommendation to Council:
--initial patron loan period
--renewal allowed for patron loan period?
--Institution loan period
--should loan periods differ by patron category?
--should loan periods differ by institution?
Schedule: Discussion at next ABC meeting, 961007, and recommendation to Council.
Update: Recommendation crafted at 961007/08 meeting. After Council discusses and informs us of the final loan period, it will be entered into the Orbis Patron Loan Rule. When the entire Loan Rule is done, each institution will enter it into their own local loan rule tables. Needs to be done shortly before Test Phase.
Council decided 3 week loans, no renewals. When III fixes the recalls/holds problem, then Council will review.
Update: 961028: Recommendation adopted by Council.
C. System tables and texts
C1. System messages and instructions: Priority: 2
III should be able to answer which we can change. Craft wording at a November ABC meeting, or via e-mail before that.
Update: Shirien will re-read documentation to find out which system messages can be changed. She will ask III again, too. If there are any, she will craft the message and submit to Committee, for discussion, editing, and recommendation to Council.
Update: Recommendation to Council approved by OBC. Council to Discuss.
Update: 961028: Recommendation adopted by Council, and another one, and another, and yet another.
C2. Overdue Notices: Priority: 2
Need to discuss # of patron od notices, and texts, and timing, and the same for the institution od notices, and texts and timing. Any notices that are seen by the public need to go to the Council. Need to talk about e-mail od notices, after we discover III's answer to I.L. above. (Anne says she thinks Orbis circ notices go out via e-mail just like the local e-mail notices do. She doesn't know about institution email notices.)
Schedule: Discussion at November 8th ABC meeting, and recommendation to Council.
Update:Maresa kindly volunteered to craft some notices for us to chew on at the next meeting. We've already done some good work on the Patron Loan Rule timings. Need to work on the Institution Loan Rule.
Update:
Recommendation to Council approved by OBC. Council to Discuss.
Update: 961028: Recommendation adopted by Council, and another one, and one last one.
C3. Location codes: Priority: 2
All Orbis libs will need to enter the institution codes into their location tables.
Schedule: Nancy or Shirien will send institutions instructions for adding codes to loc tables. Just needs to be done before test phase.
C4. Loan Rules, and Rule Selection Tables: Priority: 2
After we make all our recommendations and the Council sends us their approval or revisions, each institution will need to loan rules to their tables. (Orbis Patron Loan Rule(s), Orbis Institution Loan Rule(s), and possibly a Non Circ Loan rule, though if we already have one in our local tables, we shouldn't need this new one). Nancy and I will work with each institution when we're ready to add the loan rules to each individual system, and when we're ready to add in the appropriate entries to each local Rule Selection Table.
Schedule: Nancy and Shirien will contact institutions about adding loan rules and entries to selection tables before test phase.
Update: Can't do much more on the Patron Loan Rule until Council tells us what they want us to do for loan periods, etc.
Update: Council has pretty much adopted the policies we need to complete the patron loan rule and the Institution Loan rule. Nancy and Shirien and III will review these and will inform institutions when they should enter this info into their own tables.
C5. Paging slips: Priority: 2
Craft text of paging slip, top and bottom halves. Anybody already using paging slips, and if so, perhaps we can look at their examples.
Schedule: To be discussed at a November 8th ABC meeting.
Update: Maresa graciously agreed to craft some drafts for us. She'll e-mail them to the group.
Update:
Recommendation to Council approved by OBC. Council to Discuss.
Update:
961028:
Recommendation adopted by Council.
C6. Fines, bills, adjustment notices: Priority: 2
Need to craft fine message, billing message, and adjustment notices, and send any notices that are viewed by the public through the Council.
Schedule: To be discussed at a November 8th ABC meeting.
Update: Already discussed this in an earlier item. Closing this one since it's a dup. ITEM CLOSED
Discuss need to keep stats that system doesn't keep.
D1. Overdue fines: Priority: 1
Schedule: To be discussed at next ABC meeting, 961007, and recommendation sent to Council
Update: Recommendation about fines by institution and fines by patron type already submitted. Awaiting Council deliberation.
Update: 961028:council decided 50c/day 1st 10 days, $1/day next 15 days, max fine/item: $20. All institutions same, all ptypes same.
Update:
Recommendation to Council approved by OBC. Council to Discuss.
Update:
961028:
Recommendation adopted by Council.
D2. Generic replacement cost: Priority: 1
Schedule: To be discussed at next ABC meeting, 961007, and recommendation sent to Council
Update: Recommendation about replacement charges by institition and amount of Replacment Charge already submitted. Awaiting Council deliberation.
Update: 961028:council decided $60 replacment cost, all
institutions same.
Recommendation adopted by Council.
D3. Service charge: Priority: 1
Schedule: To be discussed at next ABC meeting, 961007, and
recommendation sent to Council
Update: Recommendation about service charges already submitted. Awaiting Council deliberation.
Update: 961028: Council decided $15 svc chrge per item. Recommendation adopted by Council.
D4. Reimbursing each institution: Priority: 3
Schedule: To be discussed at a November 8th ABC meeting and recommendation sent to Council.
Update:Think we turned this into a Priority 3 issue. Shirien is to find out more from OhioLINK, if they know anything more yet, and III. OhioLINK hasn't done anything about this yet since they planned to wait Two Years after the first Ohio libs came up before dealing with very lost books. I think this can be postponed, if it really has to, even until after we bring Orbis Borrowing Up. However, I'll keep bugging Ohio and III for answers. We do have a recommendation on this.
Update: a proposal from OBC went to Council in May, 1997. Council discussed and made policy. Orbis staff to inform OBC of policy soon.
D5. Responsibility for lost items: Priority: 5
Council should be discussing and deciding this one; ABC doesn't have to. (S's note: don't know where I got that from: maybe Jim? Anyway, it couldn't hurt for us to recommend it to them as a discussion topic for some meeting some time.) Update: 970416: S' closed this item: may be dealt with in bills/fines discussion.
After items arrive at the borrowing library by courier and before they're returned to owning library, excluding time patron has it out: if we lose it when we've borrowed it from another lib, we'll pay for its replacement cost.
E. Procedural Things
E1. Manual recalls for reserves: Priority: 1
Need to discuss manual procedure for recalls for reserve items and make recommendation for Council
Schedule: To be discussed at next ABC meeting, 961007, and recommendation sent to Council.
Update: We sent a recommendation to Council. Think we can assume they'll ok it. Shirien wrote a procedure for Committee to discuss on November 8th.
Update:
Recommendation to Council approved by OBC. Council to Discuss.
Update:
961028:
Recommendation adopted by Council.
E2. Manual recalls for patron needs: Priority: 1
Need to discuss recommendation to council about manual recalls for special patron situations
Schedule: To be discussed at next ABC meeting, 961007, and recommendation sent to Council
Update: We recommended to the Council that we not ask other libraries to make special efforts to get stuff back. If Council agrees, then Item Closed. If not, then not.
Update: 961028: Council decided not to recall items for patrons.
Council Adopted Recommendation.
E3. Competing requests: Priority: 1
Discuss and make recommendation to Council about a patron with a book in hand that already has an Orbis hold on it.
Schedule: To be discussed at next ABC meeting, 961007, and recommendation sent to Council
Update: Recommendation sent to council that patron in hand gets it.
Update: 961028: Council decided that patron with item in hands gets it. Council Adopted Policy
E4.
ILL requests that should have been AB requests: Priority: 1
Discuss and make recommendation to Council what to do if an ILL request could be filled via Orbis: staff automatically place request (if possible - PIN: III's question I.F.)
Schedule: To be discussed at next ABC meeting, 961007, and recommendation sent to Council
Update: Committee recommended to Council that ILL requests be turned into Orbis requests. If Council approves, somebody needs to tell all the ILL offices.
Update: Council tabled this recommendation. During Council discussion, it was agreed that if an Orbis library receives an ILL request from another Orbis library, that library may choose to decline to fill the ILL request
E5.
Items not available: Priority: 2
Discuss and make recommendation about procedures for handling items which are not found when paged. (automatically initiate new request for patron, if possible?) Also come to agreement on updating status in local database to missing after X days? Discuss local practice and possibly make recommendation to Council.
Schedule: to be discussed at a November 8th ABC meeting, and recommendation to Council
Update: We need to talk this one out at the November meeting. Maybe Shirien will write a procedure as a diving board for discussion. Remember that you can't cancel a request at the patron's lib: it has to be at the book's lib. That's what my notes say from III's visit. So if a patron decides he doesn't want it, the patron's lib has to contact the book's lib and tell them to cancel. And if the book's lib already mailed the book, don't cancel it.
Update: at III's Jan 22/23 training, we figured out that if an item is not available at a local site (for a multitude of reasons: missing, shouldn't have been circulate-able in Orbis in the first place due to wrong coding, etc.) we'll just cancel the request and the system will automatically attempt to re-request it from another site. If it cannot find one, a cancel hold message will be sent to the patron.
E6. Turnaround time: Priority: 1
Discuss ramifications of a 24 and a 48 hour turnaround: send information to Council about ramifications on local and other work flows for each option.
Schedule: To be discussed at next ABC meeting, 961007, and send information to Council to aid their discussion
Update: We changed the intent of the recommendation and sent it as a recommendation regarding Delivery Time. If Council approves, then Item closed.
Update: 961028: Council changed recommendation to 48 hours. Deleted wording about sat/sun/holidays. Council Adopted Policy
E7. Codified
local procedures? Priority: 2
Discuss whether there's a benefit to making agreements on # times/day we print paging slips, etc., or whether we want to leave local procedures to local libraries, as long as we agree to meet the delivery time.
Schedule: to be discussed at a November 8th ABC meeting, and recommendation to Council
Update: Can't remember for sure, but didn't we decide to let each institution figure out what it needs to do to meet delivery time? I'll put it on the agenda for the November meeting to be sure.
Update: Feb 5, 97: going to close this one. I'm pretty sure we agreed that ea inst will do what is needed to meet the goal of 48 hour turn around.
E8. Pick-Up Locations, borrowing library: Priority: 2
Need to know whether any site will want multiple pick up locations and if so, build some tables that include courier stops, etc. (p. 48 of III documentation)
Schedule: Shirien will email query to ABC, with answers due at or before a November 8th ABC meeting.
Update:Update: S sent to Committee a query about # pickup locs at each lib. When info comes back, each lib will need to fill out a Pickup Location form. This cannot be completed until we know who our courier will be and what pickup locs they will need, but libs can begin discussing how many and what labels.
E9. Pickup Locations, remote Orbis Library: Priority: 2
Need to discuss procedures for getting books to Orbis students who live in a different Orbis town than their home institution:
Schedule: E-mail discussion and maybe recommendation, or discussion at a November 8th ABC meeting with recommendation to Council.
Update: Committee discussed this and proposed a Procedure for Remote Borrowers who have access to an Orbis Library. We'll discuss at the Nov 8 meeting, and send revised procedure to Council.
Update:
Recommendation to Council approved by OBC. Council to Discuss.
Update:
961115:
Recommendation adopted by Council.
E10. Pickup Locations, no Orbis Library: Priority: 2
Need to discuss procedures for getting books to Orbis students who live in a town that does not have an Orbis Library
Schedule: E-mail discussion and maybe recommendation, or discussion at a November 8th ABC meeting with recommendation to Council.
Update: Committee discussed this and proposed a Procedure for Remote Borrowers who have access to an Orbis Library. We'll discuss at the Nov 8 meeting, and send revised procedure to Council.
Update:
Recommendation to Council approved by OBC. Council to Discuss.
Update:
961115:
Recommendation adopted by Council.
E11. Pickup Notices: Priority: 2
If the bottom half of the paging slip is what is used to notify patron, discuss each lib's options: mail slip, call patron, ignore it and train patrons to check own patron. Find out which lib's use "view own record".
Schedule: Discussion at a November 8th ABC meeting.
Update: S sent a pre-voted on Hold
Pickup Notification blurb.
Update:
Recommendation to Council approved by OBC. Council to Discuss.
Update:
961115:
Recommendation adopted by Council.
E12. Local Work Flow Models: Priority: 2
Discuss possible administrative organizations for procedures (roving band vs. ILL unit vs. Circ unit, etc.)
Schedule: Discussion at a November 8th ABC meeting. Local institutions should be discussing their plans for their work flows
Update: 970205: going to close this issue. Provided insitutions with opportunities to share local work flows but not many takers, so this may not have been all that important an issue.
E13. Processing materials: Priority: 2
Bookbands? rubber date due stamps? rubber institution stamps? pc's? barcode readers? Additional shelving? book trucks? Canvas mail bins on wheels?
Schedule: Discussion at November 8th ABC meeting, then requests for supplies from Orbis sent to NN asap, and requests for supplies not provided by Orbis sent to local institutions asap. ABC reps should involve preservation staff at local libraries in information-gathering process.
Update: Deb Cook, Carol Carr, Marilyn Kierstead, and Joanne Halgren (UO ILL) volunteered or were volunteered to form a subcom to explore these issues, as well as mailing containers, etc. They were instructed to include consideration of preservation of materials in their exporations. They may call on preservation staff expertise at some of the institutions.
Update: NNathanson ordered book bags. Bookbands at printers. Everybody responsible for ordering own date due stampers and "returned at XXX institution" stampers and about everything else they might need.
E14. Mailing: Priority: 2
Packages and boxes for transit: bubble envelopes and bags? Boxes? Preservation issues? Courier requirements for packaging may influence supplies, etc.
Schedule: Discussion at a November 8th ABC meeting, then requests for supplies from Orbis sent to NN asap, and requests for supplies not provided by Orbis sent to local institutions asap. ABC reps should Involve preservation staff at local libraries in information-gathering process. Decisions will also depend on requirements of selected courier.
Update: These issues are included in the item above E13, so ITEM CLOSED.
E15. Training documents: Priority: 2
Central training document prepared by Orbis staff. Each site tailors it to reflect local procedures. ABC to discuss needs for centralized training: System actions and operations, Orbis procedures and policies, Local procedures and work flows.
Schedule: to be discussed via e-mail and then finished at a November 8th ABC meeting.
Update: Well, we did talk about training at the Oct. meeting, and we probaby need to talk about it some more at the November meeting.
Update: 970205: Everybody seems to be doing ok with training and testing: the III training was pretty thorough, and staff at all the institutions are plugging right along with requests. NNathanson and JKopp provided a Road Show to each institution: don't know that any centralized training documents, other than these web pages, is possible or maybe even necessary. Going to close this item.
E16. Ongoing training: Priority: 2 or 3
Need to discuss staff and student worker training. Should Orbis help? Can Orbis or ABC prepare on-going training materials?
Schedule: Discussed via e-mail and maybe at a January ABC meeting.
Update:Feb 5, 97: Think I'm going to close this, because everybody seems to be doing ok on their own, and nobody brought this topic up again.
E17. Staffing levels: Priority 2
General discussion on affect this program has on staff: do sites have adequate staff for the program? Are there any things we can do for those which may not? We may not be able to do much as the ABC, but acknowledging that some sites could have some difficulty in absorbing the work is important.
Schedule: to be discussed via e-mail and then finished at a November 8th ABC meeting.
Update: This is so closely related to E12 that I'm closing it. Item Closed.
E18. Startup, staff practice: Priority: 2
Turn it on for staff to practice on: Staff actually request books from each institution in a planned and methodical way, testing the turn around time, system responses, staff responses, etc.? Test suite?
Schedule: discussion at November 8th ABC meeting. Recommendation to Council.
Update:
Nancy wrote
recommendation . We'll talk about it at Nov meeting.
Update:
Recommendation to Council approved by OBC. Council to Discuss.
Update:
961028:
Recommendation adopted by Council.
E19. Startup, patron access: Priority: 2
Everybody go live at once? Phase in?
Schedule: discussion at a November 8th ABC meeting, recommendation to Council.
Update:
E20. Post implementation communication: Priority: 3
Discuss and make recommendation to Council about each institution committing to one AB rep/institution who is the major trouble-shooter and contact for AB issues. (Contact will be ABC rep through implementation phase: need to make recommendation for long term)
Schedule: Discussion in a January ABC meeting.
Update:
961028:
Recommendation adopted by Council.
E20-1 Post implementation communication: Priority: 3
Make list of charts and tables and procedures which Orbis needs to track in perpetuity, such as:
Update:
961028:
Recommendation adopted by Council.
E21. Future new releases, local and Orbis: Priority: 5
Schedule: Discussion via email after implementation.
E.22. Scheduled closures of institution or branch: Priority: 4
Schedule: to be discussed at a January or February ABC meeting.
| Next: Explore Issue, Generate Local Conversation |
|---|
Return to
OBC
Index page
Page maintained by sstevens@darkwing.uoregon.edu