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?

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.

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?

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.