News

First qualification course on Research Data Management Plans

The qualification activities of the BioDATEN SDC started with a course on the concept and the creation of Data Management Plans: "Introduction to Research Data Management – Data Management Plans". The course held at the Computer Center in Freiburg University was jointly organized by the Freiburg Research Data Management Group and the Science Data Center BioDATEN. The course gave a brief overview of the handling of research data and different aspects of the creation of research data management plans over the complete life cycle of the respective data. The course presented concepts and strategies for the creation of DMPs in research projects to ensure the long-term re-usability and accessibility of electronic research data, including functional issues, documentation and appropriate enrichment with metadata. Furthermore, the areas of planning archiving strategies, issues on sensitive data and, last but not least, cost and refinancing models were discussed. Recommendations for Data Management Plans were given on the structure, necessary elements ranging from standard project metadata to considerations on amount of data sets, file types and software involved. Further relevant points were data and software licensing and special considerations were dedicated on data citation which might become part of future credits for research.

The course was jointly organized by the Science Data Center BioDATEN, the Freiburg Research Data Management Group represented by the eScience groups of the Computer Center and the university library. Another workshop is planned due to the high demand, as well as a broadening of the range of training courses for subject-specific questions, as is increasingly the case due to the requirements of the various research groups in the bioinformatics community.

BioDATEN present at the Research Data Management Working Group at the Stuttgart university library

The Science Data Centre BioDATEN was present at the Research Data Management Working Group (AK FDM) meeting at the Stuttgart university library to discuss the challenges of long-term identifiers. Research data management (RDM) needs to deal with objects which outlive the typical period of a project and the persons working on a research question. The identification of people needs to consider the dynamics of research, the fluctuation of researchers and ongoing technological change. These challenges need to be considered in the context of data repositories and the Science Data Centres (SDC). The person identifiers are required for information discovery on research, scholarly information and to credit scientists for the results of their research, ideally both for publication of articles and data.

The referencing of scholarly publication and sharing of data sets depends on long-term durability of identifiers. The short-term affiliation of a person with a university or a research institution contrasts this endeavour if the identity management rests upon local system or the email addresses. Thus, there is the need for stable and unambiguous references for people. Objects like papers, research data, lab notebooks and source code should be linked to one or more researchers in a proper and stable way. Ideally, the references are machine actionable. Names are problematic as they are not unique, the spelling might be incorrect and bibliographical references might vary. Researchers move around, graduate, start a PhD at a different institution or change names. Additional identifiers like email, name of the institution and department are not necessarily stable as well. The institutions’ identity management systems disambiguate but their core focus is on active members of the institution and identities are getting disabled or deleted if a person retires or moves on.

The BioDATEN project addresses the topic in the work package "1.2.4 Persistent Identifier". As the challenge is around for a while and is faced by a wide range of institutions and publishers, a couple of options are available. The "Gemeinsame Normdatei" (GND, Integrated Authority File) is such an approach for German speaking countries to a unique identifier that facilitates the collaborative use and administration of authority data. The GND represents and describes entities, i.e. persons, corporate bodies, conferences and events, geographic entities, topics as well as work relating to cultural and academic collections. The GND is primarily used by libraries to catalogue publications, but other institutions like archives, museums, cultural and (academic) institutions use GND as well. Publishers employ for example the ResearcherID which is part of the "Web of Science". It provides identifiers - the Web of Science ResearcherIDs - which are used by institutions and funders as a persistent identifier to track research output and to update publication records in Web of Science, ensuring correct author attribution and disambiguation. Another commercial approach is the Scopus Author Identifier, a proprietary solution provided by Elsevier. For identity federations, the edu-ID plays a role. Activities concerning edu-ID in Germany are coordinated by a ZKI working group. It aims for a livelong, user-centric digital identity for research and education. There are different implementations in various federations: SUNET provides eduID.se in Sweden for application and matriculation processes in higher education as well as for the creation of university user IDs. The Swiss edu-ID is the common digital identity for the academic sector.

ORCID, a novel approach to user-centric global person identifiers, started in 2010/11 by a Mellon grant and several other sponsors. It transcends discipline, geographic, national and institutional boundaries. Participation in ORCID is open to any organization that has an interest in scholarly communications. The access to ORCID services is based on transparent and non-discriminatory terms. Institutions can become members for an annual service fee, e.g. the University of Freiburg joined ORCID in February 2018. ORCID is governed by representatives from a broad cross-section of stakeholders which are by the majority not-for-profit. All software developed by ORCID will be released under a license approved by the Open Source Initiative. Researchers can create, edit, and maintain an ORCID ID and profile free of charge. Researchers control the defined privacy settings of their own ORCID. All profile data contributed to ORCID by researchers or claimed by them will be available in standard formats for free download. The availability of data is subject to the researchers' own privacy settings. ORCID identifiers and profile data are made available via free APIs and services. ORCID allows for identity federation account linking, e.g. to use Shibboleth federations. This requires the respective institution to allow ORCID as a Service Provider. ORCID itself can already act as an Attribute Provider based on OAuth2. To use this in services provided by the institution application integration is necessary. This will be discussed and evaluated for the envisioned BioDATEN services.

ORCID is already “GDPR certified”. This certification is the result of a long process initiated by the German chapter. This and its openness and independence make ORCID a prime candidate for long term person identification for BioDATEN research data sets. There are some precautious considerations: Most users are self-registered and may not be using their institution's email. There is no standardized endorsement process as an ID can be linked to institutional frameworks, but this is not required. An institutional account is difficult to distinguish from private ones. The organisation and institutional IDs are still a challenge to be unified globally. Finally, ORCID users should be aware that using ORCID has some implications: Using the ORCID API requires customising of software components. A persistent lifelong identifier allows tracking users for ever. ORCID is a US based, not-for-profit organisation, which is as such not bound to the Safe Harbour treaty. Nevertheless, it is currently the most open and viable solution available and it seems as if ORCID will become a worldwide standard. BioDATEN will strive for a coordinated solution within the State of Baden-Württemberg and opt for ORCID as the most wide spread and versatile person identifier. This could imply to add ORCID to IDM systems, provide coordinated endorsements and exchange ORCID via bwIDM federation (as an attribute).

Start of Teaching Series on Research Data Management in Bioinformatics - Workshop on Data Management Plans in Freiburg

Research processes produce an increasing amount of digital data. They are often very discipline-specific and exist in different forms. They can be the basis as well as the result of research. Preserving, managing and curating research data thus becomes a central task for every scientist and research institution - from the preparation of a research proposal to everyday research work. This process must be structured and organised. An increasingly established solution is the use of data management plans (DMP). They can primarily be understood as an abstract concept that helps to define data management through the planned course of the research project and its subsequent long-term availability.

A DMP structures the handling of research data over their life cycle. In the process, findings on required or generated data sets are to be considered as well as their licensing, enrichment with metadata, necessary processing steps and software, or ownership over time. The aim of the event is to explore the manifold questions surrounding data management and to enable the participants to create such a plan themselves. The course will cover the following topics:

  • Introduction to research data management
  • Presentation of the individual components of a data management plan: Collection of project metadata, description of the data genesis or data stock, data management, consolidation and archiving, exchange and standardization
  • Development and design of a data management plan
  • Digital data management in the research proposal
  • Presentation of online help tools (e.g. RDMO) and example DMPs (BMBF, DFG)
  • Institutional support

The course is part of the university's professional qualification programme. Application is possible via the Campus Management System.

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 => 12 ) Array(
limit => 3,
start => 12
)
$_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 => X8Z8SzENQefuo0sLkn1AQQAAAAU,
REDIRECT_SCRIPT_URL => /news,
REDIRECT_SCRIPT_URI => https://portal.biodaten.info/news,
REDIRECT_HTTPS => on,
REDIRECT_STATUS => 200,
UNIQUE_ID => X8Z8SzENQefuo0sLkn1AQQAAAAU,
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 => 42724,
REDIRECT_QUERY_STRING => limit=3&start=12,
REDIRECT_URL => /news,
GATEWAY_INTERFACE => CGI/1.1,
SERVER_PROTOCOL => HTTP/1.1,
REQUEST_METHOD => GET,
QUERY_STRING => limit=3&start=12,
REQUEST_URI => /news?limit=3&start=12,
SCRIPT_NAME => /index.php,
PHP_SELF => /index.php,
REQUEST_TIME_FLOAT => 1606843467.3174,
REQUEST_TIME => 1606843467
)
session.client.forwarded 18.213.192.104
separator .
orderBy id
orderDir asc
1 registerIP
2 access
always
renew
tracker.sid 063f6ed1db537ba3d5f8dc99c1b4891e
tracker.ssid 063f6ed1db537ba3d5f8dc99c1b4891e
tracker.rsid 063f6ed1db537ba3d5f8dc99c1b4891e
  • site 0.059 seconds (+0.059); 9.25 MB (+9.250) - afterInitialise
  • site 0.077 seconds (+0.019); 10.50 MB (+1.250) - afterRoute
  • site 0.156 seconds (+0.078); 14.25 MB (+3.750) - afterDispatch
  • site 0.169 seconds (+0.014); 14.50 MB (+0.250) - beforeRenderModule mod_custom (Footer)
  • site 0.171 seconds (+0.002); 14.50 MB (0.000) - afterRenderModule mod_custom (Footer)
  • site 0.172 seconds (+0.001); 14.75 MB (+0.250) - beforeRenderModule mod_collect (Collect)
  • site 0.173 seconds (+0.001); 14.75 MB (0.000) - afterRenderModule mod_collect (Collect)
  • site 0.173 seconds (+0.000); 14.75 MB (0.000) - beforeRenderModule mod_menu (Main Menu)
  • site 0.177 seconds (+0.004); 14.75 MB (0.000) - afterRenderModule mod_menu (Main Menu)
  • site 0.181 seconds (+0.004); 14.75 MB (0.000) - onAfterRender
  • site 0.183 seconds (+0.002); 14.75 MB (0.000) - sessionStore
15 MB

24 Queries Logged: 0.018766641616821 seconds

  1. SELECT data
      FROM `jos_session`
      WHERE `session_id` = '9750ec90112d9e5a9872b94d6a5d5eeb'
  2. DELETE
      FROM `jos_session`
      WHERE `session_id` = '9750ec90112d9e5a9872b94d6a5d5eeb'
  3. SELECT data
      FROM `jos_session`
      WHERE `session_id` = '063f6ed1db537ba3d5f8dc99c1b4891e'
  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` = '063f6ed1db537ba3d5f8dc99c1b4891e'
      LIMIT 1
  6. INSERT INTO `jos_session` (`session_id`,`client_id`,`time`,`ip`)
      VALUES ('063f6ed1db537ba3d5f8dc99c1b4891e','0','1606843467','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 17:24:27' )
      AND (`a`.`publish_down` IS NULL OR `a`.`publish_down` >= '2020-12-01 17:24:27' )
      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 17:24:27' )
      AND (`a`.`publish_down` IS NULL OR `a`.`publish_down` >= '2020-12-01 17:24:27' )
      ORDER BY `a`.`publish_up` DESC,`a`.`created` DESC
      LIMIT 12,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 17:24:27' )
      AND (`m`.`publish_down` IS NULL OR `m`.`publish_down` >= '2020-12-01 17:24:27' )
      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:1606843467;s:18:\"session.timer.last\";i:1606843467;s:17:\"session.timer.now\";i:1606843467;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:\"063f6ed1db537ba3d5f8dc99c1b4891e\";s:12:\"tracker.ssid\";s:32:\"063f6ed1db537ba3d5f8dc99c1b4891e\";s:12:\"tracker.rsid\";s:32:\"063f6ed1db537ba3d5f8dc99c1b4891e\";}',`time` = '1606843467',`ip` = '192.168.15.107'
      WHERE `session_id` = '063f6ed1db537ba3d5f8dc99c1b4891e'
  • 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