Differences between revisions 85 and 97 (spanning 12 versions)
Revision 85 as of 2022-08-03 20:19:27
Size: 3897
Editor: JakeGordon
Comment:
Revision 97 as of 2024-02-13 16:05:25
Size: 4018
Editor: JakeGordon
Comment:
Deletions are marked like this. Additions are marked like this.
Line 12: Line 12:
 * [[ABRPGenomicsTestSite|Accessing the ABRP-Genomics test site]] -- Testing changes to the ABRP Genomics site
Line 16: Line 15:
 * [[ProgramLinks|Generic Programs]]
Line 20: Line 18:
 * [[attachment:2022_08_03 Duke Data Management Protocols.pdf|Duke Data Management Protocol]] (last updated 2022-08-03)-- Protocol for maintenance of interaction data, focal sampling data, GPS/SWERB data, male ranks, dartings, and predation and human disturbance data
 * [[attachment:Princeton Data Management Protocol_Sep 2020.pdf|Princeton Data Management Protocol]] (last updated 2020-09) -- Protocol for Data Maintenance and the Demography/Reproduction Update
 * [[attachment:2023_07_03 Behav_GrpMovement Data Management Protocols.pdf|Behavioral and Group Movement Data Management Protocol]] (last updated 2023-07-03) -- Protocol for maintenance of interaction data, focal sampling data, GPS/SWERB data, male ranks, dartings, and predation and human disturbance data. Also known as the "Duke Protocol".
 * [[attachment:Census_and_Reproductive_Data_Management_Protocol.pdf|Census and Reproductive Data Management Protocol]] (last updated 2023-03-31) -- Protocol for Data Checking and the Demography/Reproduction Update
Line 23: Line 21:
 * [[attachment:Electronic Data Handling.pdf]] --See attachment for information on how electronic data are processed
 * [[attachment:Paper Data Handling.pdf]] --See attachment for information on how paper data are processed
 * [[attachment:Electronic Data Handling.pdf]] -- See attachment for information on how electronic data are processed
 * [[attachment:Paper Data Handling.pdf]] -- See attachment for information on how paper data are processed
Line 64: Line 62:
After you have logged into the database as the administrator, select the babase database. Log in to phpPgAdmin as an administrator, then select the babase database.
Line 68: Line 66:
You may have to click cancel on the process you are killing a couple of times. It will tell you that the function has failed, its just kidding! You will see a list of ongoing processes (queries, usually). Click the "Cancel" button next to whichever process you want to kill. You may have to click cancel on the process you are killing a couple of times.  It might tell you that the function has failed, but you can ignore that; it's an error in phpPgAdmin, not with Postgres.

This page is used to store codes, protocols, and procedures for use by the Data Managers.

Babase Technical Information

These links are primarly of interest to the Babase support staff.

Programs

Protocols

Wiki Administration

Copying the Babase Schema

The babase-copy-babase-schema Unix program copies the entire babase schema, including data, table definitions, validation, and everything else, from one database to another. All existing data, table definitions, validation, etc is deleted from the babase schema in the target database. You must be logged in to papio and at the Unix prompt to run the program.

The following example copies the babase schema from the babase database to the babase_test database. The first database (babase) is the database to copy from, the second (babase_test) the database to copy into.

PGPASSWORD='*********' babase-copy-babase-schema YOURADMINNAME babase babase_test
  • The ********* here would be the password of YOURADMINNAME

The next example copies the babase scheme from the babase_test database to the babase_database. The program will not copy into the babase database unless the -f (force) flag is given.

PGPASSWORD='*********' babase-copy-babase-schema -f YOURADMINNAME babase_test babase
  • When Backing up the DB, the 'help' directory can offer some direction

[YOU@papio ~]$ pg_dump --help

Killing a Process in PPA

Log in to phpPgAdmin as an administrator, then select the babase database.

There is a tab along the top of the browser window with a button for Processes. Click this button.

You will see a list of ongoing processes (queries, usually). Click the "Cancel" button next to whichever process you want to kill. You may have to click cancel on the process you are killing a couple of times. It might tell you that the function has failed, but you can ignore that; it's an error in phpPgAdmin, not with Postgres.

DataManagement (last edited 2024-06-20 14:58:32 by JakeGordon)

Wiki content based upon work supported by the National Science Foundation under Grant Nos. 0323553 and 0323596. Any opinions, findings, conclusions or recommendations expressed in this material are those of the wiki contributor(s) and do not necessarily reflect the views of the National Science Foundation.