Upload page content

You can upload content for the page named below. If you change the page name, you can also upload content for another page. If the page name is empty, we derive the page name from the file name.

File to load page content from
Page name
Comment
Name popular file data format used in Galaxy. (Once you have created your login name, please send it, and your affiliation, to outreach@galaxyproject.org. We will enable wiki editing for your account. And, by the way, you only need a wiki account to update content on this wiki. If you are looking to do analysis with Galaxy, please go to usegalaxy.org.)

Locked History Actions

Admin/Internals/ApplicationLogging

Application level logging is stored to the database in the table "event".

This table contains 6 fields:

Column

Type

Modifiers

Description

id

integer

not null default nextval('event_id_seq'::regclass)

Unique ID

create_time

timestamp without time zone

default now()

Created Time

update_time

timestamp without time zone

default now()

Last Update Time

history_id

integer

ID of history that is loaded at the time

user_id

integer

ID of user that is performing action to be logged

message

character varying(1024)

Message of action that is logged

  • Indexes:
    • "event_pkey" PRIMARY KEY, btree (id)
    Foreign-key constraints:
    • "event_user_id_fkey" FOREIGN KEY (user_id) REFERENCES galaxy_user(id)

This table can be queried using standard SQL queries. user_id and history_id can be used to track individual users and their histories, and are foreign keys to the galaxy_user and history tables.

The message field contains actual event descriptions. Below are the current messages and a brief description.

Message

Description

'Async dataid -> %s' % data_id

When an asynchronous tool is run, this logs the assigned data id

'Async executing tool %s' % tool.id

When an asynchronous tool is run, this logs the tool ID

'Async error -> %s' % STATUS

When an asynchronous tool is run, and an error occurs, this logs the status reported by the external application

"Async connecting to -> %s" % url

When an asynchronous tool is run, and the data is ready, this logs the url retrieved

"User change password"

Occurs when a user changes their password

"User change email"

Occurs when a user changes their email

"User logged in"

Occurs when a user logs in

"User logged out"

Occurs when a user logs out

"User new"

Occurs when a new user is created

"User reset password: %s" % email

Occurs when a user resets their password, records the email that the new password is sent to

"Proxy Error -> %s" % str(exc)

If UCSC proxy encounters an error, this logs the exception

"Data view: %s" % str(id)

When a user view (downloads) a dataset, the data id is recorded

"Data view as BED: %s" % str(id)

When a user views a dataset as bed (usually as custom track at UCSC, the data id is recorded

"Data edit complete: %s" % str(id)

When a user edits a dataset attributes (name, strand, etc.), the data id is recorded

"Data edit view: %s" % str(id)

When a user views a dataset attributes (name, strand, etc.), the data id is recorded

"Data delete: %s" % str(id)

When a user (without javascript) deletes a dataset the data id is recorded

"Data delete async: %s" % str(id)

When a user (with javascript) deletes a dataset the data id is recorded

"History delete: %s" % str(hid)

When a user deletes a history the history id is recorded

"History clear"

Occurs when a user clears a history.

"History share: %s to %s" % (str(history.id),str(new_history.id))

When a user shares a history, the history ids of the original and the shared history is recorded.

"History view available"

Occurs when a user views their available stored histories.

"History import: %s" % str(new_history.id)

When a user imports a history, this records the id of the newly imported history.

"History switch"

Occurs when a user switches between saved histories

"History new"

Occurs when a user creates a new history.

"History stored"

Occurs when a user saves a history.

"History renamed: %s" % str(histories[i].id)""

When a history is renamed, the id of the renamed history is recorded.

"History added to: %s to %s" % (str(data.id),str(history_id))

When a dataset is added to a history through an external web post (as in LAJ), the data id and history id is recorded.

"Tool id '%s' does not exist" % tool_id

Occurs when a tool id is passed to tool_runner, but doesn't exist ()

"Tool View: %s; %s" % (str(tool),str(params))

Called every time that a tool page is viewed. Records the tool that is viewed and the parameters that have been set at that particular view; previously existing parameters are pickled and stored as the parameter tool_state.