Differences between revisions 31 and 98 (spanning 67 versions)
Revision 31 as of 2011-01-11 19:35:11
Size: 3468
Editor: KarlPinc
Comment: There must be a bug in the wki....
Revision 98 as of 2024-06-20 14:58:32
Size: 4148
Editor: JakeGordon
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
This page will be used to store codes, protocols, and procedures for use by the Data Managers. This page is used to store codes, protocols, and procedures for use by the Data Managers.
Line 3: Line 4:
Line 6: Line 6:
 * [:RankerProgram:Ranker Program] -- The ranker program is used to develop and input Baboon social ranks.
 * [:BabaseVPN:The Babase VPN] -- The Babase Virtual Private Network is available to those people who have a Unix Login on Papio. It is primarly used to run the ranker program.
 * [:PsionFormat:The Psion Data Format] -- The Psions are handheld data collection devices. They output their data in a custom format.
 * [:BabaseChangelog:Babase 2.0 Changelog]
 * [[RankerProgram|Ranker Program]] -- The ranker program is used to develop and input Baboon social ranks.
 * [[BabaseVPN|The Babase VPN]] -- The Babase Virtual Private Network is available to those people who have a Unix Login on Papio. It is primarly used to run the ranker program.
 * [[PsionFormat|The Psion Data Format]] -- The Psions are handheld data collection devices. They output their data in a custom format.
 * [[UserManagement|User Management]]
 * [[DukeOITTools|Duke OIT Tools]]
 * [[FirewallTools|Firewall Tools]]
 * [[
BabaseChangelog|Babase 2.0 Changelog]]
 * [[SysAdmin|Systems Administration]] -- Info about how to do some common administrative tasks for our VM and our backup units.
Line 11: Line 16:
 * [:ProgramLinks:Generic Programs]
 * [:ProgramLinks:
Babase's Bespoke Programs]
 * [[ProgramLinks|Babase's Bespoke Programs]]
Line 15: Line 19:
 * [:DukeDMP:Duke's Data Management Protocol] -- Data Maintenance and Demography Update Protocols
 * attachment:Princeton%20Data%20Management%20Protocol%20Babase%201.0 -- Data Maintenance and Demography Update Protocols.
 The attached protocol is for Babase 1.0. The revised protocol for Babase 2.0 is still under
 construction. The basis of data decisions (such as maturedates and dispersedates) will not change with Babase 2.0,
 but the table input order and upload procedure will differ.
 * [[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
 * [[attachment:Data Storage.pdf]] -- See attachment for information on how data that come from the field are stored
 * [[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
 * [[GeneticTableForms|Forms for adding new data to the genetics tables]]
Line 21: Line 26:
 * [:DukeIDEP:Duke's Interaction Data Entry Protocol] -- Specific to Grooming, MCE, and Agonisms
Line 27: Line 31:
 * EmailManagement
Line 30: Line 34:
 * [:TabbyTest:Tabby's test page]  * [[TabbyTest|Tabby's test page]]
Line 32: Line 36:
 * MultiPartyInteractionDevelopment
Line 35: Line 38:
 * [:WritingAComplexQuery]

[[Anchor(newuser)]]
=== Adding a User to Babase ===

 * Users can be added to babase, as well as a schema created, and permissions set, by completing the following steps using a SSH client.
{{{
PGPASSWORD='*********' babase-user-add USERNAME babase_readers}}}

 * The ********* here would be the babase_admin password
 * The Username selected will become not only the babase username and temporary password but also the schema name.
 * It is very important that the user immediately change their password using PPA's password change option.
 * [[WritingAComplexQuery]]
 * ExtendedQuizQuestions
 * [[attachment:Historic Agonism Summary.xls]]
Line 49: Line 43:
Line 53: Line 46:
Line 54: Line 48:
PGPASSWORD='*********' babase-copy-babase-schema babase babase_test}}}
 * The ********* here would be the babase_admin password
PGPASSWORD='*********' babase-copy-babase-schema YOURADMINNAME babase babase_test
}}}
 * The ********* here would be the password of YOURADMINNAME
Line 58: Line 53:
Line 59: Line 55:
PGPASSWORD='*********' babase-copy-babase-schema -f babase_test babase}}} PGPASSWORD='*********' babase-copy-babase-schema -f YOURADMINNAME babase_test babase
}}}
 * When Backing up the DB, the 'help' directory can offer some direction
Line 61: Line 59:
{{{
[YOU@papio ~]$ pg_dump --help
}}}
=== Killing a Process in PPA ===
Log in to phpPgAdmin as an administrator, then select the babase database.
Line 62: Line 65:
 * When Backing up the DB, the 'help' directory can offer some direction
{{{
[YOU@papio ~]$ pg_dump --help}}}
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.

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.