[118] in iswork
Announcing an updatable IS Work database
daemon@ATHENA.MIT.EDU (Tim McGovern)
Fri Sep 22 21:48:47 2000
Message-ID: <39CC0BAA.48041DCC@mit.edu>
Date: Fri, 22 Sep 2000 21:47:22 -0400
From: Tim McGovern <tjm@MIT.EDU>
Reply-To: tjm@MIT.EDU
MIME-Version: 1.0
To: itlt@mit.edu
CC: iswork@mit.edu
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi all --
I am pleased to announce that the IS Work database is live, and
available for all of you to peruse, and to update, as appropriate. To
access the database, go to http://mit.edu/is/work/.
The old Project DB information as of Sep 18th has migrated to the IS
Work database, and sits alongside the Theme, Strategy and Initiatives
information that has been developed over the last year. A couple of
comments on the projects that we migrated. First, we intend to make the
default display be only active, planned and on hold projects. This
mirrors how the default Project DB page. Terminated and completed
projects are in the new database, available from a link on the projects
page. Second, the projects are not yet linked to their respective
initiatives. Bob has graciously volunteered to take a first crack at
making those links. When this occurs the initiative links in the
project pages will be active, and the linked projects will appear on the
relevant initiative's page.
What else remains for us to do? There are a few pages in the IS Web
site that still have links to the old Project DB. As we gain confidence
over the next week or so in the IS Work database, we will be changing
those links to point to IS Work. There are a few minor functional
improvements (for example searching across the entire database) that
remain on our "punch list." We encourage you to add items to that list
by using the database, and sending your comments to <iswork@mit.edu>.
Finally, after we complete these last few tasks, we will be physically
moving the system into an appropriate production service environment.
To reiterate what Kris said a couple of weeks ago, the security right
now for updating the database is dependent on a weaker approach than we
are accustomed to at MIT. When you are committing an update, you will
be prompted for a username and password. We suggest that you enter your
username in the first text box, and enter "itltedit" in the second one.
This will have the effect of recording in the database which of you have
made the change, and when. Rest assured, we will revisit the security
method continuously as progress is made on the issue of Filemaker
security.
Any questions, please don't hesitate to get in touch with me.
Tim
