From bwm@nova.npac.syr.edu Wed Mar 6 19:58 EST 1996 Received: from nova.npac.syr.edu (bwm@nova.npac.syr.edu [128.230.7.2]) by postoffice.npac.syr.edu (8.7.1/8.7.1) with ESMTP id TAA23680; Wed, 6 Mar 1996 19:58:20 -0500 (EST) Received: (from bwm@localhost) by nova.npac.syr.edu (8.7.1/8.7.1) id TAA14481; Wed, 6 Mar 1996 19:58:19 -0500 (EST) Date: Wed, 6 Mar 1996 19:58:19 -0500 (EST) From: Barbara Mihalas Message-Id: <199603070058.TAA14481@nova.npac.syr.edu> To: kea@npac.syr.edu Subject: Re: database Cc: bwm@nova.npac.syr.edu Content-Type: text Content-Length: 2009 Status: R Terri, I have created the entire new framework that will enable a logical update structure. Am finishing the code that will load the data correctly into the new tables and revising the code to fit the new table and record structure. It is going well, but the speed is limited by my other commitments which take too many hours per day. There is a new entry on the initial page where you access the database link. It currently links to a combination of old and new, but will be the location of the fully functional version. The other one wasn't working because I had revised the low level routines and then all the other packages that call functions from there needed to be reloaded. I have reloaded everything now. You should be able to enter records ok using the old version. DON'T enter anything into the new on until I tell you it's OK! I'm not sure what it would do ... Thanks, Barbara And please keep sending me the notes. I hope to have the revision done in 1-2 days, but have meeting all morning tomorrow ... and unpredictable interruptions otherwise. >From kea@nova.npac.syr.edu Wed Mar 6 19:34 EST 1996 Received: from nova.npac.syr.edu (kea@nova.npac.syr.edu [128.230.7.2]) by postoffice.npac.syr.edu (8.7.1/8.7.1) with ESMTP id TAA23517 for ; Wed, 6 Mar 1996 19:34:36 -0500 (EST) Received: (from kea@localhost) by nova.npac.syr.edu (8.7.1/8.7.1) id TAA14128 for bwm; Wed, 6 Mar 1996 19:34:35 -0500 (EST) Date: Wed, 6 Mar 1996 19:34:35 -0500 (EST) From: Theresa Canzian Message-Id: <199603070034.TAA14128@nova.npac.syr.edu> To: bwm@nova.npac.syr.edu Subject: database Content-Type: text Content-Length: 321 Status: R Hi Barbara, It seems that we are still not able to even enter new records into the database. Also, we can't update anything either. I suppose you are probably too well aware of all of this, but thought I'd drop you a line just in case you think it's all working. Sorry for the disappointing news. Take Care, Terri From bwm@nova.npac.syr.edu Sun Mar 31 18:23 EST 1996 Received: from nova.npac.syr.edu (bwm@nova.npac.syr.edu [128.230.7.2]) by postoffice.npac.syr.edu (8.7.5/8.7.1) with ESMTP id SAA27571; Sun, 31 Mar 1996 18:23:56 -0500 (EST) Received: (from bwm@localhost) by nova.npac.syr.edu (8.7.1/8.7.1) id SAA28763; Sun, 31 Mar 1996 18:23:55 -0500 (EST) Date: Sun, 31 Mar 1996 18:23:55 -0500 (EST) From: Barbara Mihalas Message-Id: <199603312323.SAA28763@nova.npac.syr.edu> To: bwm@nova.npac.syr.edu, kea@nova.npac.syr.edu, njm@nova.npac.syr.edu, paulc@nova.npac.syr.edu Subject: SCCS database Content-Type: text Content-Length: 1170 Status: R Nancy, Terri, Paul, This database needs some serious user testing at this point. The first thing to try is the new data input using the technical report input form. Note that if you select a document type of "contract" or any of the publication types and also elect to store the record and not just look at it, then the return screen will have a form for input of contract or publication information. I am still finishing the update stuff, but I would appreciate if you would look at some of that. In particular the "List and update documents by Document Type and SCCS number" is new and makes it easy to go through and update just publication info for all documents of a particular publication type. The update forms all work, but the processing of them is still being debugged. Took time out from development to start documenting everything. Will send first file of documentation next. Please let me know about everything that either doesn't work at all (like all the update processing) or needs some tuning to be convenient or usable or whatever. If you can identify by URL and screen name, that would be very helpful. Thanks, Barbara From bwm@npac.syr.edu Sun Mar 31 18:24 EST 1996 Received: from kayak.npac.syr.edu (kayak-fddi.npac.syr.edu [128.230.8.70]) by postoffice.npac.syr.edu (8.7.5/8.7.1) with ESMTP id SAA27584; Sun, 31 Mar 1996 18:24:43 -0500 (EST) Received: (bwm@localhost) by kayak.npac.syr.edu (8.6.7/8.6.6) id SAA54962; Sun, 31 Mar 1996 18:24:42 -0500 From: Barbara Mihalas Date: Sun, 31 Mar 1996 18:24:42 -0500 Message-Id: <199603312324.SAA54962@kayak.npac.syr.edu> To: bwm@npac.syr.edu, kea@npac.syr.edu, njm@npac.syr.edu, paulc@npac.syr.edu Subject: doc on howto make it Content-Type: text Content-Length: 5960 Status: R To populate an Oracle database table with all fields and records from the Filemaker Pro database 1. Dump all records from filemaker pro sorted by sccs number, with all fields. Use tab-separated export. Fetch the recordexport to kayak directory: /export/project/kyk28/webdb/rdbms/oracle/kayak/httpd/httpd/sccsnew1 2. Do export in merge mode with all fields in same order as 1. Dump no records or select only a small number. Only the comma-separated field list will be used by the perl script that processes. Fetch the fieldexport to kayak directory: /export/project/kyk28/webdb/rdbms/oracle/kayak/httpd/httpd/sccsnew1 3. Go to directory /export/project/kyk28/webdb/rdbms/oracle/kayak/httpd/httpd/sccsnew1 on kayak. 4. Edit sccsparams.dat. SCCSFIELDS: must be followed by the filename of the fieldexport. SCCSDAT: must be followed by the filename of the recordexport. Give the output files new names if desired. These follow DBTABLES: NEWDAT: and CTLFILE: Change the delimiters only if different export options are chosen. 5. Run fnmerge.pl best to redirect debug output to debug file. (eg fnmerge.pl > fn.debug ) If necessary, rename database table (currently sccsq). This can be done by editing this name in fnmerge.pl or by editing the sccstbl.sql file after running fnmerge.pl. (I'll probably change sccsparams.dat to include the name of the output database file, too. be simpler) fnmerge.pl creates scripts and control files, sql to make the database table and a file of processed data ready to load into the table. Then type run1a to run all the scripts fnmerge.pl writes that will create the database table and load the processed data into the table. 6. Or, after database name is OK, just type run1 This will run fnmerge.pl and then run all the scripts that fnmerge.pl produces to create and load the processed data into the database table. To locate and get the pathnames for all the online sccs documents and abstracts: TeX version, Postscript version, HTML version and HTML abstract. Then add these locations to the database table. 1. Go to directory on nova /home/R6F/bwm/rdbms/httpd/sccs 2. Edit furls1.pl to change the output filename $ffile if desired, (currently set to url_update1.dat at line 42) and to update the value of $sccsmax to the current maximum SCCS number. (currently set to 755 at line 40) 3. Run furls1.pl 4. Copy output file (eg url_update1.dat) to kayak directory /export/project/kyk28/webdb/rdbms/oracle/kayak/httpd/httpd/oraperl 5. Edit lines 38-41 of parsurl.pl if necessary to change the names of input and output files and the name of the database table where the file locations will be updated. 7. Run parsurl.pl to produce a .sql file (currently updateurls1.sql) that has a set of update commands, one for each SCCS number. 8. Get into sql*plus as bwm and run the .sql file (eg updateurls1.sql) produced by parsurl.pl. at the sql*plus prompt >, type > @updateurls1 and then wait a long time while it runs through update and commit on every file in the database. To create the real SCCS Oracle Database tables from the filemaker pro dump, 1. Run .sql files that set up the tables with primary keys, foreign keys and constraints. These are currently the following files in the following directories: /export/project/kyk28/webdb/rdbms/oracle/kayak/httpd/httpd/plsql_bwm/sccsresnv/sccs_tables history_tables.sql shared_tables.sql and /export/project/kyk28/webdb/rdbms/oracle/kayak/httpd/httpd/plsql_bwm/sccsresnv/sccsa_tables sccsa_tables.sql sccsb_tables.sql puba_tables.sql pubb_tables.sql sccsx_seq.sql DATA INPUT TABLES AND SEQUENCES FOR ONLINE ENTRY OF NEW RECORDS sccsb_tables.sql pubb_tables.sql The sccsb_tables and pubb_tables are the basic record, contract record and publication record data input tables for online input from a web browser. They are for new records only. New records can be input, viewed and revised. They will then be reviewed by one of the database oversight group (see next paragraph) and transferred to the permanant Oracle SCCS database environment (sccsa and puba tables). ORACLE SCCS DATABASE TABLES AND SEQUENCES FOR LOCATING AND VIEWING INFORMATION ABOUT SCCS DOCUMENTS. ALSO FOR ONLINE UPDATE OF PUBLICATION INFORMATION sccsa_tables.sql puba_tables.sql The sccsa_tables and puba_tables are populated only by the original procedural transfer from the Oracle filemaker pro table OR from a transfer from the sccsb online input environment. The transfer is allowed only by a select group of database overseers, which currently will include Terri Canzian, Nancy McCracken, Barbara Mihalas and Paul Coddington. TABLES AND SEQUENCES FOR CHECKING PASSWORDS, AND FOR TRACKING USE, NEW RECORD CREATION, AND RECORD UPDATES history_tables.sql shared_tables.sql sccsx_seq.sql These are all populated only from private procedures in the database code. They are invisible to users, except for some report links made available through the web browser interface. 2. To populate from the Oracle table of the filemaker pro export, see BWM. This requires running a procedure called RESQ2A_CLEANUP.cleanup. It will populate the basic SCCS document table, the contract report table and a table for each of the basic publication types: journal submission, conference proceedings, book, book chapter, and phd thesis. In the process, it will produce a consistent designation of document type, and store the value in the field document_type. It also populates two tables with obsolete filemaker pro data in its original form in case needed for future reference. From bwm@npac.syr.edu Sun Mar 31 18:25 EST 1996 Received: from kayak.npac.syr.edu (kayak-fddi.npac.syr.edu [128.230.8.70]) by postoffice.npac.syr.edu (8.7.5/8.7.1) with ESMTP id SAA27593; Sun, 31 Mar 1996 18:25:24 -0500 (EST) Received: (bwm@localhost) by kayak.npac.syr.edu (8.6.7/8.6.6) id SAA55734; Sun, 31 Mar 1996 18:25:23 -0500 From: Barbara Mihalas Date: Sun, 31 Mar 1996 18:25:23 -0500 Message-Id: <199603312325.SAA55734@kayak.npac.syr.edu> To: kea@npac.syr.edu, njm@npac.syr.edu, paulc@npac.syr.edu Subject: will try to write more .. Cc: bwm@npac.syr.edu Content-Type: text Content-Length: 92 Status: R on how to use the database this evening. have some other things to do also tho. b. From bwm@npac.syr.edu Sun Mar 31 18:27 EST 1996 Received: from kayak.npac.syr.edu (kayak-fddi.npac.syr.edu [128.230.8.70]) by postoffice.npac.syr.edu (8.7.5/8.7.1) with ESMTP id SAA27621; Sun, 31 Mar 1996 18:27:42 -0500 (EST) Received: (bwm@localhost) by kayak.npac.syr.edu (8.6.7/8.6.6) id SAA41151; Sun, 31 Mar 1996 18:27:42 -0500 From: Barbara Mihalas Date: Sun, 31 Mar 1996 18:27:42 -0500 Message-Id: <199603312327.SAA41151@kayak.npac.syr.edu> To: kea@npac.syr.edu, njm@npac.syr.edu, paulc@npac.syr.edu Subject: url Cc: bwm@npac.syr.edu Content-Type: text Content-Length: 168 Status: R the database software that needs testing is at http://kayak.npac.syr.edu:6398/ and it's the link "Restricted access SCCS database: Reorganized Tables" b. From bwm@nova.npac.syr.edu Mon Apr 1 12:17 EST 1996 Received: from nova.npac.syr.edu (bwm@nova.npac.syr.edu [128.230.7.2]) by postoffice.npac.syr.edu (8.7.5/8.7.1) with ESMTP id MAA03277; Mon, 1 Apr 1996 12:17:29 -0500 (EST) Received: (from bwm@localhost) by nova.npac.syr.edu (8.7.1/8.7.1) id MAA23589; Mon, 1 Apr 1996 12:17:28 -0500 (EST) Date: Mon, 1 Apr 1996 12:17:28 -0500 (EST) From: Barbara Mihalas Message-Id: <199604011717.MAA23589@nova.npac.syr.edu> To: kea@nova.npac.syr.edu, nora@nova.npac.syr.edu Subject: SCCS title pages Cc: bwm@nova.npac.syr.edu Content-Type: text Content-Length: 227 Status: R The pages that Nora couldn't find appear all to be talks, so have no real document accompanying them. They are: 442. 426. 325. 323. 315. 314. 303, 301 Let me know if there are further questions about them. --Barbara From njm@oldnova.npac.syr.edu Mon Apr 1 17:10 EST 1996 Received: from oldnova.npac.syr.edu (root@oldnova.npac.syr.edu [128.230.7.4]) by postoffice.npac.syr.edu (8.7.5/8.7.1) with ESMTP id RAA05842; Mon, 1 Apr 1996 17:10:57 -0500 (EST) Received: from oldnova.npac.syr.edu (njm@oldnova.npac.syr.edu [128.230.7.4]) by oldnova.npac.syr.edu (8.7.1/8.7.1) with SMTP id RAA05999; Mon, 1 Apr 1996 17:10:56 -0500 (EST) From: Nancy McCracken Message-Id: <199604012210.RAA05999@oldnova.npac.syr.edu> X-Authentication-Warning: oldnova.npac.syr.edu: Host njm@oldnova.npac.syr.edu [128.230.7.4] didn't use HELO protocol To: Barbara Mihalas Cc: njm@oldnova.npac.syr.edu, paulc@oldnova.npac.syr.edu, kea@oldnova.npac.syr.edu Subject: Re: SCCS database In-reply-to: Your message of "Sun, 31 Mar 96 18:23:55 EST." <199603312323.SAA28763@nova.npac.syr.edu> Date: Mon, 01 Apr 96 17:10:54 EST Content-Type: text Content-Length: 2049 Status: R > This database needs some serious user testing at this point. > > The first thing to try is the new data input using the technical > report input form. > > Note that if you select a document type of "contract" or any of > the publication types and also elect to store the record and not > just look at it, then the return screen will have a form for input > of contract or publication information. > > I am still finishing the update stuff, but I would appreciate if you > would look at some of that. In particular the > "List and update documents by Document Type and SCCS number" is new > and makes it easy to go through and update just publication info > for all documents of a particular publication type. Barbara, Great work. I had fun looking at this. Here are comments on small things: First of all, in the top level, you need to print what is the last document number so that people can add one to get the next free document number. In the input data form: RESA_TECH.input_record There is a top section labelled "You must fill out these fields", and I'm not sure that all of them require filling out. What about fields 3-6, version number and source sccs doc information? That seems optional. Also, at the bottom of this section is a field ISBN number, which probably shouldn't even be here - it probably goes with book chapter. Is there any particular way that the date should be formatted, or are you prepared to cope with most forms? Under optional fields, I guess that I would prefer that Approved for WWW had yes for default. It seems the most likely option. I'm not sure that I understand about the submitted by, submission status, etc.? Does this mean submitted as an SCCS report? Or is this where you put things like "Submitted to the IEEE Conference on Geriatric Web Documents", which, by the way, sometimes needs to be printed along with the technical report reference. Oops, Geoffrey just asked me to make up homework problems for his class tonight - guess I'll look at the other parts later! Nancy