News

BioDATEN participating in the state wide RDM WG meeting (12.05.)

Representatives of the Science Data Center BioDATEN took part in the RDM Working Group (AK FDM) online meeting on 12th May 2020 and contributed to the discussion both on quality assurance and governance of research data.
The long-term character of research data and the various parties involved in the process create new challenges in research organisations with a high level of fluctuation in personnel. The researchers who created, collected and processed data may have left the research institution and projects were officially completed long ago. Many projects are also confronted with questions regarding copyright, handling of personal data and appropriate licenses for research data. Responsibility for the data must therefore be exercised in a regulated manner at any point in the data lifecycle by appropriate entities. After using service providers for storing and processing data during the project period, other entities can get involved after the project ends like subject-specific repositories or university publication services such as dark archives. The potentially perpetual storage of data after project completion is accompanied by responsibilities whose assignment should be clarified. Part of the handling can be derived from data management plans, other parts could be defined in research data policies of the scientific institution.

Research data management also affects aspects of good scientific practice. With the objective of achieving the greatest possible transparency and openness while at the same time considering the prudent handling of sensitive data, this requires clear regulations and agreements. For example, questions of copyright and the handling of personal data should already be clarified at the start of a research project or project in general. The same goes for the granting of suitable licenses for research data taken over by storage facilities, like repositories or dark archives, or data generated by researchers.
BioDATEN as a science data center should therefore help it's community by suggesting guidelines and promote their implementation. These include the question of data release and regulations comparable to publication contracts with the University Library. Increasingly, an (institutionalised) RDM is becoming a prerequisite for the approval of grants for new research projects. In order to ensure that this does not remain a one-sided process, both individual researchers and the research institutions and its entities, such as research groups, institutes or CRCs, must be included in the governance considerations for the RDM.

In the following, a document with guidelines for practical aspects of the RDM will be compiled for individual professorships and individual working groups as well as for larger collaborative projects. These should contain clear regulations on costs and responsibility including the assignment of rights to the storage facility in cases such as data migration and deletion. Early planning is facilitated by filling out Data Management Plans. This makes it possible to plan costs and expenses for the infrastructure providers involved.

(DvS,HG)

BioDATEN joined three working groups for cross-cutting topics

The Science Data Center BioDATEN is actively involved in the SDC's cross-cutting activities in Baden-Württemberg coordinated by the bw2FDM project. On Wednesday, 2nd April three online meetings were held which were dedicated to the topics of legal support, business models, and meta data. BioDATEN was present both in the role as contributor and consumer through various participants from Tübingen and Freiburg. In the discussion of the group, possible objectives of the legal working group got outlined, ranging from the creation of a discussion platform and a network for recommendations of action to the preparation of workshops, trainings, FAQs, checklists, handouts, knowledge bases, and model contracts. Further on, the activities in other states with regard to legal issues in RDM will be monitored. Of course, general advice with regard to legal issues in specific individual cases is problematic. The individual research institutions are primarily responsible to provide this. The working group reiterated the importance of cooperation of the technical and the legal sides. The next meeting will primarily deal with the legal implications of data sharing and reusing.

Business and operation models are definitely a relevant cross-cutting topic as many state sponsored projects and state-wide services share the same set of challenges including sustainable financing and the assignment of required personnel on non-existing permanent positions.
The BioDATEN project is aware of this as in the precursor ViCE projects which have also addresses aspects on operation and business models.
Theses aspects have already been elaborated but not solved. A certain base might be provided by the already existing cooperation framework existing in today's regulations (check for suitable legal entities and cooperation frameworks). Another option is the tight cooperation and coordination with ongoing NFDI activities like the DataPLANT NFDI for fundamental plant research for parts of the BioDATEN communities. For sustainable operation qualified staff plays a key role as well as the provisioning of storage systems for the data.

The third online meeting addressed the cross-cutting topic of metadata. Metadata are very important throughout the complete lifecycle of research data. While there are basic, descriptive metadata that are very likely to be shared across communities like author, DOI, affiliation etc. there are also very domain and research specific metadata like species, treatment, experimental design etc. Descriptive metadata are best handled by using established standards like DataCite. Research specific metadata are probably best coped with by using existing ontologies. Researches can than pick the label that describes their data best. Additionally, there are technical and process related metadata. To a large extend, both can be collected automatically during the data processing on HPC resources or by tools like FITS. The well established PREMIS framework is a good solution to capture technical metadata.
These four kinds of metadata must be containerised into one file. The METS framework offers such a container and is also well established.
A special role plays the usage of ORCID as a method to reference authors, contributors etc. Unlike institution-based identity management, ORCID is person-based and every researcher can update their affiliation and contact information. This comes in handy as soon as researchers leave their home institution and are no longer reachable under the institution’s email address.

(DvS,HG)

New workshop on research data management

The Science Data Center BioDATEN is getting more and more involved in outreach and training activities in research data management. Since (junior) scientists are usually actively involved in research projects, corresponding courses should take place at the beginning of the research project if possible, so that the life cycle of the research data can be covered almost completely. Thus, the computing center of the Freiburg University is planning a full-day workshop for the CIBBS research group, a research cluster granted in the German university excellency initiative and for the bio-chemistry research training group on 25th April in Freiburg. The teaching and qualification measures are geared towards junior researchers at the beginning of their career with the aim to work towards a well thought-out and structured data and workflow preparation. The workshop follows the idea to avoid time consuming and error-prone end-of-project data management by providing advice to researchers at an early stage in the life cycle of data. Data sets should be curated with the vision of later publication from the beginning, enriched with proper metadata and converted into sustainable file formats. Junior scientists need an increasing amount of qualified knowledge to access the various advanced research infrastructures and to properly handle the associated data management.

The workshop as planned will be a combined information and training event to give an introduction to domain-specific research data management focusing on the cluster of excellence at the university of Freiburg (CIBBS) and further groups from the bioinformatics and bio-chemistry domains. They offer concrete instructions in day-to-day activities. Researchers are introduced to methodological, organizational, technical and legal challenges of research data management on the one hand, and on the other hand specific requests of the working group are dealt with. Further topics covered will encompass: Presentation of the respective research approaches and the associated RDM, learn from current procedures and workflows as examples (best practices) for the own work, learn of available and planned infrastructures and future developments in BioDATEN, creation and use of ORCID IDs, tools and methods for data management (hands-on; e.g. use of restic, rucio).

Further (outreach) events focus on groups like the Bioinformatics Club of senior PIs at the university of Freiburg. The presentation planned will give an overview on the ongoing activities and developments in BioDATEN and training and summer school activities of Galaxy and ELIXIR/EOSC.
Beside practical aspects of data management the outreach event will give an introduction to the planned bwSFS (Storage-for-Science) system as a future base for data storage, long-term archiving and publication. It will advocate for concepts like the ORCID ID to improve descriptive metadata for data publication. The qualification of PIs is to be regarded as particularly important, since these generate on the one hand a lot of data and are responsible for the reusability of these. On the other hand, these senior researchers in their role as supervisors for students and doctoral students serve as an example and should therefore adopt a sustainable approach to research data, for which BioDATEN will provide the necessary framework.

Sponsored by:

  • Ministerium für Wissenschaft, Forschung und Kunst Baden-Württemberg
  • Ministerium für Wissenschaft, Forschung und Kunst Baden‑Württemberg

Debug Console

Close15 MBRequestSessionTimelineDatabase24Events25
$_GET
Array( limit => 3, start => 3 ) Array(
limit => 3,
start => 3
)
$_POST
Array( ) Array(

)
$_COOKIE
Array( ) Array(

)
$_SERVER
Array( USER => apache, HOME => /usr/share/httpd, FCGI_ROLE => RESPONDER, REDIRECT_UNIQUE_... Array(
USER => apache,
HOME => /usr/share/httpd,
FCGI_ROLE => RESPONDER,
REDIRECT_UNIQUE_ID => X8aKCzENQefuo0sLkn1ARAAAAAU,
REDIRECT_SCRIPT_URL => /news,
REDIRECT_SCRIPT_URI => https://portal.biodaten.info/news,
REDIRECT_HTTPS => on,
REDIRECT_STATUS => 200,
UNIQUE_ID => X8aKCzENQefuo0sLkn1ARAAAAAU,
SCRIPT_URL => /news,
SCRIPT_URI => https://portal.biodaten.info/news,
HTTPS => on,
HTTP_USER_AGENT => CCBot/2.0 (https://commoncrawl.org/faq/),
HTTP_ACCEPT => text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8,
HTTP_ACCEPT_LANGUAGE => en-US,en;q=0.5,
HTTP_ACCEPT_ENCODING => br,gzip,
HTTP_HOST => portal.biodaten.info,
HTTP_X_FORWARDED_PROTO => https,
HTTP_X_FORWARDED_FOR => 18.213.192.104,
HTTP_CONNECTION => close,
PATH => /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin,
SERVER_SIGNATURE => ,
SERVER_SOFTWARE => Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips,
SERVER_NAME => portal.biodaten.info,
SERVER_ADDR => 192.168.15.64,
SERVER_PORT => 443,
REMOTE_ADDR => 192.168.15.107,
DOCUMENT_ROOT => /var/www/biodatenhub4,
REQUEST_SCHEME => https,
CONTEXT_PREFIX => ,
CONTEXT_DOCUMENT_ROOT => /var/www/biodatenhub4,
SERVER_ADMIN => root@localhost,
SCRIPT_FILENAME => /var/www/biodatenhub4/index.php,
REMOTE_PORT => 51444,
REDIRECT_QUERY_STRING => limit=3&start=3,
REDIRECT_URL => /news,
GATEWAY_INTERFACE => CGI/1.1,
SERVER_PROTOCOL => HTTP/1.1,
REQUEST_METHOD => GET,
QUERY_STRING => limit=3&start=3,
REQUEST_URI => /news?limit=3&start=3,
SCRIPT_NAME => /index.php,
PHP_SELF => /index.php,
REQUEST_TIME_FLOAT => 1606846987.8178,
REQUEST_TIME => 1606846987
)
session.client.forwarded 18.213.192.104
separator .
orderBy id
orderDir asc
1 registerIP
2 access
always
renew
tracker.sid b9d600128ba039e788d30a7e1d4e8d16
tracker.ssid b9d600128ba039e788d30a7e1d4e8d16
tracker.rsid b9d600128ba039e788d30a7e1d4e8d16
  • site 0.071 seconds (+0.071); 9.25 MB (+9.250) - afterInitialise
  • site 0.093 seconds (+0.022); 10.50 MB (+1.250) - afterRoute
  • site 0.178 seconds (+0.085); 14.50 MB (+4.000) - afterDispatch
  • site 0.191 seconds (+0.013); 14.50 MB (0.000) - beforeRenderModule mod_custom (Footer)
  • site 0.192 seconds (+0.001); 14.50 MB (0.000) - afterRenderModule mod_custom (Footer)
  • site 0.193 seconds (+0.000); 14.75 MB (+0.250) - beforeRenderModule mod_collect (Collect)
  • site 0.194 seconds (+0.001); 14.75 MB (0.000) - afterRenderModule mod_collect (Collect)
  • site 0.194 seconds (+0.000); 14.75 MB (0.000) - beforeRenderModule mod_menu (Main Menu)
  • site 0.197 seconds (+0.003); 14.75 MB (0.000) - afterRenderModule mod_menu (Main Menu)
  • site 0.199 seconds (+0.003); 14.75 MB (0.000) - onAfterRender
  • site 0.203 seconds (+0.003); 15.00 MB (+0.250) - sessionStore
15 MB

24 Queries Logged: 0.020298719406128 seconds

  1. SELECT data
      FROM `jos_session`
      WHERE `session_id` = 'a0b2b3999cf1795fcf5f6c338aa9ab91'
  2. DELETE
      FROM `jos_session`
      WHERE `session_id` = 'a0b2b3999cf1795fcf5f6c338aa9ab91'
  3. SELECT data
      FROM `jos_session`
      WHERE `session_id` = 'b9d600128ba039e788d30a7e1d4e8d16'
  4. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_languages'
  5. SELECT session_id
      FROM `jos_session`
      WHERE `session_id` = 'b9d600128ba039e788d30a7e1d4e8d16'
      LIMIT 1
  6. INSERT INTO `jos_session` (`session_id`,`client_id`,`time`,`ip`)
      VALUES ('b9d600128ba039e788d30a7e1d4e8d16','0','1606846987','192.168.15.107')
  7. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_members'
  8. SELECT b.id
      FROM `jos_usergroups` AS `a`
      LEFT JOIN jos_usergroups AS b
      ON b.lft <= a.lft
      AND b.rgt >= a.rgt
      WHERE `a`.`id` = '1'
  9. SELECT *
      FROM `jos_viewlevels`
  10. SELECT folder AS type,element AS name,protected,params
      FROM `jos_extensions`
      WHERE `enabled` >= '1'
      AND `type` = 'plugin'
      AND `state` >= '0'
      AND `access` IN ('1','1','4')
      ORDER BY `ordering` ASC
  11. SELECT m.id,m.menutype,m.title,m.alias,m.note,m.path AS route,m.link,m.type,m.level,m.language,m.browserNav,m.access,m.params,m.home,m.img,m.template_style_id,m.component_id,m.parent_id,e.element AS component
      FROM `jos_menu` AS `m`
      LEFT JOIN jos_extensions AS e
      ON e.extension_id = m.component_id
      WHERE `m`.`published` = '1'
      AND `m`.`parent_id` > '0'
      AND `m`.`client_id` = '0'
      ORDER BY `m`.`lft` ASC
  12. SELECT jos_template_styles.id,jos_template_styles.home,jos_template_styles.template,jos_template_styles.params,jos_extensions.protected
      FROM `jos_template_styles`
      INNER JOIN jos_extensions
      ON jos_extensions.element = jos_template_styles.template
      WHERE `jos_template_styles`.`client_id` = '0'
      AND `jos_extensions`.`enabled` = '1'
      AND `jos_extensions`.`type` = 'template'
      AND jos_extensions.`client_id` = `jos_template_styles`.`client_id`
      ORDER BY `home` DESC
  13. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_content'
  14. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_categories'
  15. SELECT a.rules
      FROM `jos_assets` AS `a`
      WHERE `a`.`id` = '1'
      GROUP BY a.id, a.rules, a.lft
  16. SELECT b.rules
      FROM `jos_assets` AS `a`
      LEFT JOIN jos_assets AS b
      ON b.lft <= a.lft
      AND b.rgt >= a.rgt
      WHERE `a`.`name` = 'com_content'
      GROUP BY b.id, b.rules, b.lft
      ORDER BY `b`.`lft` ASC
  17. SELECT c.*,
      CASE WHEN CHAR_LENGTH(c.alias) THEN CONCAT_WS(':', c.id, c.alias) ELSE c.id END as slug,COUNT(i.`id`) AS numitems
      FROM `jos_categories` AS `c`
      LEFT JOIN jos_categories AS s
      ON (s.lft <= c.lft
      AND s.rgt >= c.rgt) OR (s.lft > c.lft
      AND s.rgt < c.rgt)
      LEFT JOIN (SELECT cat.id as id
      FROM jos_categories AS cat JOIN jos_categories AS parent
      ON cat.lft BETWEEN parent.lft
      AND parent.rgt
      WHERE parent.extension = 'com_content'
      AND parent.published != 1
      GROUP BY cat.id) AS badcats
      ON badcats.id = c.id
      LEFT JOIN `jos_content` AS i
      ON i.`catid` = c.id
      AND i.state = 1
      WHERE (`c`.`extension` = 'com_content' OR `c`.`extension` = 'system' )
      AND `c`.`access` IN ('1','1','4')
      AND `c`.`published` = '1'
      AND `s`.`id` = '26'
      AND badcats.id is null
      GROUP BY c.id,c.asset_id,c.access,c.alias,c.checked_out,c.checked_out_time,c.created_time,c.created_user_id,c.description,c.extension,c.hits,c.language,c.level,c.lft,c.metadata,c.metadesc,c.metakey,c.modified_time,c.note,c.params,c.parent_id,c.path,c.published,c.rgt,c.title,c.modified_user_id
      ORDER BY `c`.`lft` ASC
  18. SELECT b.rules
      FROM `jos_assets` AS `a`
      LEFT JOIN jos_assets AS b
      ON b.lft <= a.lft
      AND b.rgt >= a.rgt
      WHERE `a`.`name` = 'com_content.category.26'
      GROUP BY b.id, b.rules, b.lft
      ORDER BY `b`.`lft` ASC
  19. SELECT a.*,a.id,a.title,a.alias,a.title_alias,a.introtext,a.language,a.checked_out,a.checked_out_time,a.catid,a.created,a.created_by,a.created_by_alias,
      CASE WHEN a.modified IS NULL THEN a.created ELSE a.modified END AS modified,a.modified_by,uam.name AS modified_by_name,
      CASE WHEN a.publish_up IS NULL THEN a.created ELSE a.publish_up END AS publish_up,a.publish_down,a.images,a.urls,a.attribs,a.metadata,a.metakey,a.metadesc,a.access,a.hits,a.featured,a.xreference,a.fulltext AS readmore,
      CASE WHEN badcats.id is not null THEN 0 ELSE a.state END AS state,c.title AS category_title,c.path AS category_route,c.access AS category_access,c.alias AS category_alias,
      CASE WHEN a.created_by_alias > ' ' THEN a.created_by_alias ELSE ua.name END AS author,ua.email AS author_email,parent.title AS parent_title,parent.id AS parent_id,parent.path AS parent_route,parent.alias AS parent_alias,ROUND(v.rating_sum / v.rating_count, 0) AS rating,v.rating_count AS rating_count,c.published,
      CASE WHEN badcats.id is null THEN c.published ELSE 0 END AS parents_published
      FROM `jos_content` AS `a`
      LEFT JOIN jos_content_frontpage AS fp
      ON fp.content_id = a.id
      LEFT JOIN jos_categories AS c
      ON c.id = a.catid
      LEFT JOIN jos_users AS ua
      ON ua.id = a.created_by
      LEFT JOIN jos_users AS uam
      ON uam.id = a.modified_by
      LEFT JOIN jos_categories as parent
      ON parent.id = c.parent_id
      LEFT JOIN jos_content_rating AS v
      ON a.id = v.content_id
      LEFT
      OUTER JOIN (SELECT cat.id as id
      FROM jos_categories AS cat JOIN jos_categories AS parent
      ON cat.lft BETWEEN parent.lft
      AND parent.rgt
      WHERE parent.extension = 'com_content'
      AND parent.published != 1
      GROUP BY cat.id) AS badcats
      ON badcats.id = c.id
      WHERE `a`.`access` IN ('1','1','4')
      AND `c`.`access` IN ('1','1','4')
      AND
      CASE WHEN badcats.id is null THEN a.state ELSE 0 END IN (1)
      AND `a`.`catid` = '26'
      AND (`a`.`publish_up` IS NULL OR `a`.`publish_up` <= '2020-12-01 18:23:08' )
      AND (`a`.`publish_down` IS NULL OR `a`.`publish_down` >= '2020-12-01 18:23:08' )
      ORDER BY `a`.`publish_up` DESC,`a`.`created` DESC
      LIMIT 9223372036854775807
  20. SELECT a.*,a.id,a.title,a.alias,a.title_alias,a.introtext,a.language,a.checked_out,a.checked_out_time,a.catid,a.created,a.created_by,a.created_by_alias,
      CASE WHEN a.modified IS NULL THEN a.created ELSE a.modified END AS modified,a.modified_by,uam.name AS modified_by_name,
      CASE WHEN a.publish_up IS NULL THEN a.created ELSE a.publish_up END AS publish_up,a.publish_down,a.images,a.urls,a.attribs,a.metadata,a.metakey,a.metadesc,a.access,a.hits,a.featured,a.xreference,a.fulltext AS readmore,
      CASE WHEN badcats.id is not null THEN 0 ELSE a.state END AS state,c.title AS category_title,c.path AS category_route,c.access AS category_access,c.alias AS category_alias,
      CASE WHEN a.created_by_alias > ' ' THEN a.created_by_alias ELSE ua.name END AS author,ua.email AS author_email,parent.title AS parent_title,parent.id AS parent_id,parent.path AS parent_route,parent.alias AS parent_alias,ROUND(v.rating_sum / v.rating_count, 0) AS rating,v.rating_count AS rating_count,c.published,
      CASE WHEN badcats.id is null THEN c.published ELSE 0 END AS parents_published
      FROM `jos_content` AS `a`
      LEFT JOIN jos_content_frontpage AS fp
      ON fp.content_id = a.id
      LEFT JOIN jos_categories AS c
      ON c.id = a.catid
      LEFT JOIN jos_users AS ua
      ON ua.id = a.created_by
      LEFT JOIN jos_users AS uam
      ON uam.id = a.modified_by
      LEFT JOIN jos_categories as parent
      ON parent.id = c.parent_id
      LEFT JOIN jos_content_rating AS v
      ON a.id = v.content_id
      LEFT
      OUTER JOIN (SELECT cat.id as id
      FROM jos_categories AS cat JOIN jos_categories AS parent
      ON cat.lft BETWEEN parent.lft
      AND parent.rgt
      WHERE parent.extension = 'com_content'
      AND parent.published != 1
      GROUP BY cat.id) AS badcats
      ON badcats.id = c.id
      WHERE `a`.`access` IN ('1','1','4')
      AND `c`.`access` IN ('1','1','4')
      AND
      CASE WHEN badcats.id is null THEN a.state ELSE 0 END IN (1)
      AND `a`.`catid` = '26'
      AND (`a`.`publish_up` IS NULL OR `a`.`publish_up` <= '2020-12-01 18:23:08' )
      AND (`a`.`publish_down` IS NULL OR `a`.`publish_down` >= '2020-12-01 18:23:08' )
      ORDER BY `a`.`publish_up` DESC,`a`.`created` DESC
      LIMIT 3,3
  21. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_search'
  22. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_users'
  23. SELECT m.id,m.title,m.module,m.position,m.content,m.showtitle,m.params,mm.menuid,e.protected
      FROM `jos_modules` AS `m`
      LEFT JOIN jos_modules_menu AS mm
      ON mm.moduleid = m.id
      LEFT JOIN jos_extensions AS e
      ON e.element = m.module
      AND e.client_id = m.client_id
      WHERE `m`.`published` = '1'
      AND `e`.`enabled` = '1'
      AND (`m`.`publish_up` IS NULL OR `m`.`publish_up` <= '2020-12-01 18:23:08' )
      AND (`m`.`publish_down` IS NULL OR `m`.`publish_down` >= '2020-12-01 18:23:08' )
      AND `m`.`access` IN ('1','1','4')
      AND `m`.`client_id` = '0'
      AND (`mm`.`menuid` = '153' OR `mm`.`menuid` <= '0' )
      ORDER BY `m`.`position` ASC,`m`.`ordering` ASC
  24. UPDATE `jos_session`
      SET `data` = '__default|a:10:{s:15:\"session.counter\";i:1;s:19:\"session.timer.start\";i:1606846987;s:18:\"session.timer.last\";i:1606846987;s:17:\"session.timer.now\";i:1606846987;s:24:\"session.client.forwarded\";s:14:\"18.213.192.104\";s:8:\"registry\";O:23:\"Hubzero\\Config\\Registry\":2:{s:7:\"\0*\0data\";O:8:\"stdClass\":1:{s:1:\"0\";s:7:\"session\";}s:9:\"separator\";s:1:\".\";}s:4:\"user\";C:17:\"Hubzero\\User\\User\":22:{a:1:{s:5:\"guest\";b:1;}}s:11:\"tracker.sid\";s:32:\"b9d600128ba039e788d30a7e1d4e8d16\";s:12:\"tracker.ssid\";s:32:\"b9d600128ba039e788d30a7e1d4e8d16\";s:12:\"tracker.rsid\";s:32:\"b9d600128ba039e788d30a7e1d4e8d16\";}',`time` = '1606846988',`ip` = '192.168.15.107'
      WHERE `session_id` = 'b9d600128ba039e788d30a7e1d4e8d16'
  • onAfterInitialise Method plgSystemP3p::onAfterInitialise /core/plugins/system/p3p/p3p.php:21
  • onAfterInitialise Method plgSystemRemember::onAfterInitialise /core/plugins/system/remember/remember.php:20
  • onAfterInitialise Method plgSystemHubzero::onAfterInitialise /core/plugins/system/hubzero/hubzero.php:21
  • onAfterInitialise Method plgSystemXFeed::onAfterInitialise /core/plugins/system/xfeed/xfeed.php:21
  • onAfterInitialise Method plgSystemSupergroup::onAfterInitialise /core/plugins/system/supergroup/supergroup.php:113
  • onAfterInitialise Method plgSystemReferrerpolicy::onAfterInitialise /core/plugins/system/referrerpolicy/referrerpolicy.php:21
  • onAfterRoute Method plgSystemJquery::onAfterRoute /core/plugins/system/jquery/jquery.php:21
  • onAfterRoute Method plgSystemSpamjail::onAfterRoute /core/plugins/system/spamjail/spamjail.php:21
  • onAfterRoute Method plgSystemIncomplete::onAfterRoute /core/plugins/system/incomplete/incomplete.php:21
  • onAfterRoute Method plgSystemUnconfirmed::onAfterRoute /core/plugins/system/unconfirmed/unconfirmed.php:21
  • onAfterRoute Method plgSystemUnapproved::onAfterRoute /core/plugins/system/unapproved/unapproved.php:21
  • onAfterRoute Method plgSystemPassword::onAfterRoute /core/plugins/system/password/password.php:21
  • onContentPrepare Method plgContentLoadmodule::onContentPrepare /core/plugins/content/loadmodule/loadmodule.php:35
  • onContentPrepare Method plgContentEmailcloak::onContentPrepare /core/plugins/content/emailcloak/emailcloak.php:25
  • onContentPrepare Method plgContentPagebreak::onContentPrepare /core/plugins/content/pagebreak/pagebreak.php:35
  • onContentPrepare Method plgContentXhubtags::onContentPrepare /core/plugins/content/xhubtags/xhubtags.php:25
  • onContentPrepare Method plgContentFormatwiki::onContentPrepare /core/plugins/content/formatwiki/formatwiki.php:63
  • onContentPrepare Method plgContentFormathtml::onContentPrepare /core/plugins/content/formathtml/formathtml.php:105
  • onContentPrepare Method plgContentExternalhref::onContentPrepare /core/plugins/content/externalhref/externalhref.php:41
  • onContentBeforeDisplay Method plgContentPagenavigation::onContentBeforeDisplay /core/plugins/content/pagenavigation/pagenavigation.php:25
  • onContentBeforeDisplay Method plgContentVote::onContentBeforeDisplay /core/plugins/content/vote/vote.php:32
  • onAfterDispatch Method plgSystemMobile::onAfterDispatch /core/plugins/system/mobile/mobile.php:22
  • onAfterDispatch Method plgSystemDebug::onAfterDispatch /core/plugins/system/debug/debug.php:60
  • onAfterDispatch Method PlgSystemHighlight::onAfterDispatch /core/plugins/system/highlight/highlight.php:25
  • onAfterRender Method plgSystemSef::onAfterRender /core/plugins/system/sef/sef.php:21