Managing Track Hubs with the Registry - The Dashboard

When you register, you're immediately logged in into the system and presented the so called dashboard, a web interface which allows to explore and edit the track data hubs that you submit to the Registry. The interface is divided into three tabbed panels: "Profile", "My track collections" and "Submit/Update". The last one is intended to support track hub submission from the web. This functionality is not yet available, but will be in the near future. At the moment, the panel contains a reminder of the possibility of using the REST API.

Viewing and Editing Track Hubs

When you login into the registry using the web interface, the default panel which is shown is named "My track collections". It provides a quick overview of the data hubs you've submitted to the Track Hub registry. An imaginary example is shown below:

Each line refers to track database settings for a given assembly in a given hub submitted to the Registry. Id is the ID of the corresponding JSON document as stored in the Registry; Hub and Assembly are respectively the name of the Hub and the assembly the database refers to; Created/Updated are the dates at which the hub was submitted to/updated in the Registry; Status shows a label about the status of the track database as know to the Registry, which can be:

"Unknown": the Registry has not yet checked the status of the hub and the tracks in the database;
"All is well": hub and all track data files as available;
"Remote data unavailable": some or all of the remote track data is unavailable.

The last two come with the date at which the check was performed. The last column presents buttons for doing some actions depending on the status of the track database. When status reports "Remote data unavailable", you can click on the spyglass icon to access information about the reasons, like in the following:

The report will show a summary of the track database, with the hub name, species and assembly, the total number of tracks in the database and the number of them linked to remote data. For these, the report at the bottom presents a list with the name of the track, the URL of the remote binary indexed data file and the reason why it cannot be accessed.

Independently of the status, there's an icon showing a trash bin which can be clicked to delete the corresponding track database from the Registry. As discussed in Modelling Track Hubs, a track data hub is implicitly represented by the set of trackDb documents which refer to it. Similarly to the REST API, in order to completely remove a track hub from the Registry, it is necessary to delete all track databases belonging to the same hub.

Updating Your Profile

Click on the "Profile" tab label to access a page where you can view/update the details of your account profile.

You cannot change your username, but you can edit your first/last name and affiliation (optional), the email used for communication from the Registry and the password to authenticate with the website and the REST API.

Automatic Track Hub Monitoring

You may have noticed a section "Track Hub monitoring configuration" when you signed up in the registration form. The same appears in the profile update form. The Registry performs periodic checks on the status of the tracks data files referred to in the submitted track hubs and, based on these, it updates the status of the corresponding track databases appearing on the search result page and on the track collection tab in the dashboard.

You can control two parameters related to these periodic inspections:

Check interval: tells the Registry the frequency with which to perfom the check. If set to Automatic the decision is left to the Registry;
Receive continuos alerts: if the checkbox is not ticked, you receive an alert message about some faulty tracks only once.

As stated before, the Registry sends an alert message to the profile's email address at the end of each inspection in case something wrong is found with the track data files of your submitted data hubs, and unless you've ticked the checkbox above.