The "Ditto" project seems to have disappeared from Project Office Dashboard. Betty said that it had been included in "Sirsi Oracle Migration." That's fine, except that the definition of that project does not include the specifics of the backup and restore found in "Ditto." Should we pull the project team together to create a new definition of the project?

There are still many stories going on in OIT in this regard. I believe this will get cleaned up as the product line comes into focus.

In the interim, what can we do to make sure that this doesn't disappear?

The project "HBLL Imaging Problem (Altiris Imaging)" was closed, but I don't feel that the issues were addressed. I've asked Jim to have it re-opened.

Per your request, I asked for that project to be closed and a new one opened called "HBLL-Multicasting." That project will be a predecessor to a follow-on project that will investigate restricted campus-wide multicasting. You can follow that project by looking at project 15 HBLL-Multicasting (Corsair) currently in the investigation folder in project office.

Multi-casting and the issues of performance between the north and south buildings are to a certain extent independent and linking them together will likely cause problems in the future. For instance, Kelly has been very clear that multicasting in the library is temporary. We don't have a long term commitment to provide multicasting in the building. Second, multicasting is only one possible solution to the Altiris problem mentioned in the original project. I'd rather not have that project closed when we don't actually have a solution to the problem. Would you be willing to re-open "HBLL Imaging Problem (Altiris Imaging)" until the problem is fully resolved?

Bill needs to meet with Mel Smith of the College of Humanities to see if there is any interest.

• Find last year's agreement
• Update it with support for servers
• Review funding model
• Review with Brett
• Review with Nabil
• Review with Randy and Julene
• Take to David Monsen
• Take to Jon Mott.

Taylor Snyder, who was managing the wireless projects, has been off sick for quite sometime.  He is back today.  He reports that the engineering is done but Bart is waiting for antennas.  Taylor will update Project Office as soon as he can.  He has a lot of catching up to do so give him a couple days to get the updates into Project Office.

I want a map showing the locations of all of the wireless access points in the ceilings so that we can support the system. I turned in an AHD request #644806.

Emailed Nyle asking how we track progress.

• Status of ERes
• do they need remoteauth?
• do they need proxy?

• What type of metadata will Google use to index our site?
• Google Hacks says that if you get into DMOZ that you have a better chance of being indexed. Should we be getting individual collections into DMOZ?
• How much and how deep is Google searching in our web space?
• We should call the U to see what they are doing.
• Are there ways to direct Google to what we want them to see?

• Julene and Bill will talk to Dick Hacken about getting library links on his pages.
• Scott Eldredge will add metadata to the collection pages and in the alt tags for images to describe the collections.
• Scott Eldredge will submit our collection webpages to DMOZ for indexing.

Another thing that we can do is make sure that the titles of our collection pages match the content. Many search engines use this as a major factor in indexing the site.

• 9 months ago VPN was added to Morton and Orleck, locking out the library
• At some point OIT changed the firewall configuration on Zoram so that Unicorn stopped working
• This week OiT changed the security profile on Toledo (a CID server) and locked out Nabil

I've sent an email to Rex Franson suggesting this.

Betty Walling says that this project is supposed to be closed because we had the close out meeting. Brett points out that it was not closed because the testing never occured. This is partially our fault since we don't have the room built yet.

Brett is asking for 2 GB to the server room.

There is a need for another project to investigate the throughput between the library and the CPC for video capture.

In parallel I am conversing with Bill Holman. I wrote:

The project "HBLL Imaging Problem (Altiris Imaging)" was closed, but I don't feel that the issues were addressed. I've asked Jim to have it re-opened.

Per your request, I asked for that project to be closed and a new one opened called "HBLL-Multicasting." That project will be a predecessor to a follow-on project that will investigate restricted campus-wide multicasting. You can follow that project by looking at project 15 HBLL-Multicasting (Corsair) currently in the investigation folder in project office.

Multi-casting and the issues of performance between the north and south buildings are to a certain extent independent and linking them together will likely cause problems in the future. For instance, Kelly has been very clear that multicasting in the library is temporary. We don't have a long term commitment to provide multicasting in the building. Second, multicasting is only one possible solution to the Altiris problem mentioned in the original project. I'd rather not have that project closed when we don't actually have a solution to the problem. Would you be willing to re-open "HBLL Imaging Problem (Altiris Imaging)" until the problem is fully resolved?

• We need to integrate our support tree with that being developed by CID to hand off first level support to OIT.
• Since support with OIT will be using AHD to track and resolve problems, the library will need to use AHD. At this point we're just going to have Jacob Jenson and Bill Lund have access until the point that more people need access.

Randy and Julene were open to the idea of formally supporting DSpace as part of the library's open source initiative.

Attending: USU, Eccles, UofU, BYU

Eccles: they reinstalled. Letting departments decide on what they would like to do. Links to digital collections. Faculty publications and presentations. Departmental publications, annual reports. Looking at publishers that allow authors to put up the final version of their documents. This is not the pdf of the publisher’s version. Will need to do the work for the submitters. They are looking at creating a batch utility for DSpace. This is possible, but is at the Unix prompt. They are looking at a better interface.

State Library: documents of the state agencies.

What is next? Poll the directors to see if there is a need for UALC presence. If so, then who is going to develop and support it, funding too. Until up and going with the projects, we may not be able to say what the value is. What are their expectations? Demo of what we’ve been able to do.

Demo what the three libraries are doing. I need to email to Ruth Hansen a report on what we have done. Met, shared info, mail list. In the summer issue invitation to view. Next meeting of DSpace working group after 5/6 meeting. Looking at authority control. Looking at batch loading. GWLA project wants a distributed repository, OAI responders and harvesters.

• Crow, Raym. The Case for Institutional Repositories: A SPARC Position Paper. SPARC. Retrieved 11/14/2003 from http://www.arl.org/sparc/IR/ir.html
• Johnson, Richard K., Institutional Repositories, Partnering with Faculty to Enhance Scholarly Communication. D-Lib Magazine, (November 2002). Retrieved 11/14/2003 from http://www.dlib.org/dlib/november02/johnson/11johnson.html
• Lynch, Clifford A. Institutional Repositories: Essential Infrastructure for Scholarship in the Digital Age. ARL Bimonthly Report 226 (February 2003). Retrieved 11/14/2003 from http://www.arl.org/newsltr/226/ir.html

I decided to delete all of the documents from the repository and start from scratch. So any old documents will need to be resubmitted."

1. HBLL we investigate why our own public machines are inconsistent, specifically, some of the open machines are limited to BYU sites and others are not.
2. We will determine what Family History wants to be doing
3. Once everything is as consistent as it is going to be, and we have determined our own policies, we will document them.
4. We will review the document with Bill Holman and come to an agreement.
5. Bill Holman will take the agreed upon document to Kelly McDonald for a formal exception to the policy against open computers.

• As a formal government document repository, we are required to provide services to all community patrons.
• In our agreements with UALC we are required to provide services to all patrons from UALC institutions.
• As a formal family history library of the Church we are required to provide services to all family history patrons.

• Unicorn migration to Oracle.
• Restoring Zeilin backup to Morton for testing
• Improving intrabuilding networking.

• Restoring Zeilin backup to Morton for testing
• Intrabuilding multicasting

The current projects are: Sirsi Oracle Conversion (Professional Services), HBLL Backup and Restore (Ditto) (Investigations), and HBLL Imaging Problem (Altiris) (Investigations).