Versionen im Vergleich

Schlüssel

  • Diese Zeile wurde hinzugefügt.
  • Diese Zeile wurde entfernt.
  • Formatierung wurde geändert.

...

Scripts Documentation

Single line comments start with --

...

--We have published . 
Issue 2023
where setting_name = 'issueID' and setting_value = 13
Issue 2022
where setting_name = 'issueID' and setting_value = 8

get-authors-and-submissions.sql

authors-registration.sql

05-01_authors_registration.sql

...

On the making

Scripts we have not yet managed to finish.

  • ...

Quick useful queries

-- Given submission_id, provide the backend and frontend links of its submission. Change 368 for your n.

SELECT p.submission_id,

p.publication_id,

CONCAT('https://journals.phl.univie.ac.at/meicogsci/workflow/access/', p.submission_id) as 'url_backend',

CONCAT('https://journals.phl.univie.ac.at/meicogsci/article/view/', p.submission_id) as 'url_frontend'

FROM publications p

WHERE p.submission_id = 368

-- WHERE p.publication_id = 328

...

Given a list of emails, returns a table with all the submissions by those authors, the user_id, givenName, familyName, email, university, publication_id, submission_id, title (of the abstract), abstract, last_modified (date), and a quick access URL to the public view and the dashboard view of that submission.

get-authors-email-family_name-given_name.sql

Smaller script: Returns the email, family name and given name of an author, which are values found at different tables of the database (email in users and names in user_settings).

get-author-id-by-email.sql

Smaller script: Returns the author_id, given name, family name, email, university, publication_id, submission_id and country, given an email address.

get-urls_submission-id.sql

Smaller script: Generates the URLs for quick access of a given submission both in the public face of the website (or its preview) and the admin dashboard.

get-submissions-date-range.sql

Gets submissions within a date range and their data. 

This is important as a constrain because until the submissions have been reviewed and approved, we cannot filter them by issue (merely because they have not yet been assigned to an issue, which is a manual process done one by one).


On the making

Scripts we have not yet managed to finish, if any.

  • 05-01_authors_registration.sql
    • We would like it to track: Author, email address, submission ID (& link), submission title, if the submission abstract text field is filled, and if they actually pressed the button to submit).

Quick useful queries

-- Given submission_id, provide the backend and frontend links of its submission. Change 368

SELECT a.email, a.author_id, a.publication_id

FROM authors a

WHERE email = (SELECT email FROM authors WHERE author_id = "270")

-- Given one of the user's author_id, show their data (familyName, givenName, affiliation, country) for both publications. Change 270 for your n.

SELECT p.submission_id,

p. DISTINCT a.email, a.author_id, a.publication_id, ase.setting_value

FROM authors a, author_settings ase

JOIN (SELECT author_id, setting_value FROM author_settings WHERE author_id = "270") as aaf

ON ase.author_id = aaf.author_id

WHERE email = (SELECT email FROM authors WHERE author_id = "270")

-- Check which users have the permission most tutors had.

SELECT * FROM authors WHERE user_group_id = 36;

Annexes

Tables used

These are the tables in our database.

  1. Most of these might be empty or merely not used. 
  2. We highlight in bold the ones we have been using in successful queries.
  3. We highlight in italics the ones in which we have found data that we have not yet managed to explain, but which may become relevant.

CONCAT('https://journals.phl.univie.ac.at/meicogsci/workflow/access/', p.submission_id) as 'url_backend',

CONCAT('https://journals.phl.univie.ac.at/meicogsci/article/view/', p.submission_id) as 'url_frontend'

FROM publications p

WHERE p.submission_id = 368

-- WHERE p.publication_id = 328

-- Given one of the user's author_id, show their email and both publications. Change 270 for your n.

SELECT a.email, a.author_id, a.publication_id

FROM authors a

WHERE email = (SELECT email FROM authors WHERE author_id = "270")


-- Given one of the user's author_id, show their data (familyName, givenName, affiliation, country) for both publications. Change 270 for your n.

SELECT DISTINCT a.email, a.author_id, a.publication_id, ase.setting_value

FROM authors a, author_settings ase

JOIN (SELECT author_id, setting_value FROM author_settings WHERE author_id = "270") as aaf

ON ase.author_id = aaf.author_id

WHERE email = (SELECT email FROM authors WHERE author_id = "270")


-- Check which users have the permission most tutors had.

SELECT * FROM authors WHERE user_group_id = 36;


Annexes

Tables used

These are the tables in our database.

  1. Most of these might be empty or merely not used. 
  2. We highlight in bold the ones we have been using in successful queries.
  3. We highlight in italics the ones in which we have found data that we have not yet managed to explain, but which may become relevant.
  • Authors
  • access_keys
  • announcement_settings
  • announcement_type_settings
  • announcement_types
  • announcements
  • auth_sources
  • author_settings
  • authors
  • books_for_review
  • books_for_review_authors
  • books_for_review_settings
  • captchas
  • categories
  • category_settings
  • citation_settings
  • citations
  • comments
  • completed_payments
  • controlled_vocab_entries
  • controlled_vocab_entry_settings
  • controlled_
  • Authors
  • access_keys
  • announcement_settings
  • announcement_type_settings
  • announcement_types
  • announcements
  • auth_sources
  • author_settings
  • authors
  • books_for_review
  • books_for_review_authors
  • books_for_review_settings
  • captchas
  • categories
  • category_settings
  • citation_settings
  • citations
  • comments
  • completed_payments
  • controlled_vocab_entries
  • controlled_vocab_entry_settings
  • controlled_vocabs
  • custom_issue_orders
  • custom_section_orders
  • data_object_tombstone_oai_set_objects
  • data_object_tombstone_settings
  • data_object_tombstones
  •  dataverse_files
  •  dataverse_studies
  •  edit_assignments
  •  edit_decisions
  •  email_log
  •  email_log_users  
  •  email_templates
  •  email_templates_default
  •  email_templates_default_data
  •  external_feeds 
  •  external_feed_settings 
  •  email_templates_settings 
  •  event_log 
  •  event_log_settings 
  •  failed_jobs
  •  files 
  •  filter_groups 
  •  filter_settings 
  •  filters 
  •  genre_settings 
  •  genres 
  •  group_memberships 
  •  group_settings 
  •  groups 
  •  institutional_subscription_ip 
  •  institutional_subscriptions 
  •  issue_files 
  •  issue_galley_settings 
  •  issue_galleys 
  •  issue_settings 
  •  issues 
  •  item_views 
  •  jobs 
  •  journal_settings 
  •  journals 
  •  library_file_settings 
  •  library_files 
  •  metadata_description_settings 
  •  metadata_descriptions 
  •  metrics 
  •  mutex 
  •  navigation_menu_item_assignment_settings 
  • navigation_menu_item_assignments
  •  navigation_menu_item_settings 
  •  navigation_menu_items 
  •  navigation_menus 
  •  notes 
  •  notification_mail_list 
  •  notification_settings 
  •  notification_subscription_settings 
  •  notifications 
  •  oai_resumption_tokens 
  •  object_for_review_assignments 
  •  object_for_review_persons 
  •  object_for_review_settings 
  •  objects_for_review 
  •  paypal_transactions 
  •  pln_deposit_objects 
  •  pln_deposits 
  •  plugin_settings 
  •  processes 
  •  publication_categories 
  •  publication_galley_settings 
  •  publication_galleys 
  •  publication_settings 
  •  publications 
  •  queries 
  •  query_participants 
  •  queued_payments 
  •  referral_settings 
  •  referrals 
  •  review_assignments 
  •  review_files 
  •  review_form_element_settings
  •  referral_settings 
  •  referrals 
  •  review_assignments 
  • review_files
  • review_form_element_settings
  •  review_form_elements           
  •  review_form_responses                    
  •  review_form_settings 
  •  review_forms 
  •  review_object_metadata 
  •  review_object_metadata_settings 
  •  review_object_type_settings 
  •  review_object_types 
  •  review_round_files 
  •  review_rounds 
  •  roles 
  •  rt_contexts 
  •  rt_searches 
  •  rt_versions 
  •  scheduled_tasks 
  •  section_settings 
  •  sections 
  •  sessions 
  •  site 
  •  site_settings 
  •  stage_assignments 
  •  static_page_settings 
  •  static_pages 
  •  subeditor_submission_group 
  •  submission_artwork_files 
  •  submission_comments 
  •  submission_file_revisions 
  •  submission_file_settings 
  •  submission_files 
  •  submission_search_keyword_list 
  •  submission_search_object_keywords
  •  submission_search_objects 
  •  submission_settings 
  •  submission_supplementary_files 
  •  submission_tombstones 
  •  submission_xml_galleys 
  •  submissions 
  •  subscription_type_settings 
  •  subscription_types 
  •  subscriptions 
  •  temporary_files 
  •  theses 
  •  usage_stats_temporary_records 
  •  user_group_settings 
  •  user_group_stage 
  •  user_groups 
  •  user_interests 
  •  user_settings 
  •  user_user_groups 
  •  users 

...

*Eli's note for the 2025 team:
Before May, create a new review form for 2025 and assign it as the default to the Talk and Poster sections. You will save yourselves the task of assigning it manually for every reviewer for every submission, about 360 times ;) This new review form has to include the minimal textual changes required and agreed in the Coordination-Consortium meeting June 2024 (you may ask @Lisl or check the notes stored in the MEi:CogSci Consortium Google Drive). 

> TAB: CATEGORIES

Eli's note for the 2025 team:
We don't know what they do. But have a look at their possibilities on "how to order articles in this category: Title (A-Z)" to see if we could avoid the task or reordering all the articles manually just before publishing the issue.
For more info: https://docs.pkp.sfu.ca/learning-ojs/en/journal-setup#categories

SETTINGS: WEBSITE

In this section there are many many tabs, sometimes inside of other tabs. This is why we will structure this section on the wiki not by tabs but by where you can find each feature, so it's most helpful slightly smiling face 

Design

Change some of the design of the homepage, how the whole website looks and how to customize its design:

...

the

...

MEi:CogSci

...

Consortium Google Drive). 

...

-Favicon (customized to MEi:CogSci, tiny image in the Internet browser tab)

Image Removed

...

...

...

-Journal Style Sheet (which we have not tried, but may allow CSS?)

...

> TAB: CATEGORIES

Eli's note for the 2025 team:
We don't know what they do. But have a look at their possibilities on "how to order articles in this category: Title (A-Z)" to see if we could avoid the task or reordering all the articles manually just before publishing the issue.
For more info: https://docs.pkp.sfu.ca/learning-ojs/en/journal-setup#categories

SETTINGS: WEBSITE

In this section there are many many tabs, sometimes inside of other tabs. This is why we will structure this section on the wiki not by tabs but by where you can find each feature, so it's most helpful slightly smiling face 

Design

Change some of the design of the homepage, how the whole website looks and how to customize its design:

WhatWhere
-Font. 
SETTINGS: WEBSITE > APPEARANCE > THEME: "Typography".
-Logo.SETTINGS: WEBSITE > APPEARANCE > SETUP: "Logo".
-Background color for the header(MEi:CogSci color). SETTINGS: WEBSITE > APPEARANCE > THEME: "Colour".
-Content of the header. (It's just the Logo)
-Content of the footer. 
SETTINGS: WEBSITE > APPEARANCE > SETUP: "Page Footer".

-Favicon (customized to MEi:CogSci, tiny image in the Internet browser tab)

Image Added

...

...

-Journal Style Sheet (which we have not tried, but may allow CSS?)

> APPEARANCE >> ADVANCES
















Menus & URLs

Change the structure/architecture/navigation (what page is inside of which and its URL) of the website:

-Main menu ("Primary Navigation Menu").

Image Added

Menus & URLs

Change the structure/architecture/navigation (what page is inside of which and its URL) of the website:

-Main menu ("Primary Navigation Menu").

Image Removed

SETTINGS: WEBSITE (on the left bar) > SETUP (upper tab) > NAVIGATION (left-central tab)

-Secondary menu ("User Navigation Menu").

Image Removed

-Right Sidebar elements in the homepage (Language Toggle Block: "Deutsch, English", Information Block "For Readers, For Authors, For Librarians", Developed By Block "Open Journal Systems" and a Subscription Block that actually doesn't appear, right?)SETTINGS: WEBSITE (on the left bar) > APPEARANCE SETUP (upper tab) > SETUP NAVIGATION (left-central tab inside) > Scroll to the bottom.

Eli's note:

...

-Secondary menu ("User Navigation Menu").

Image Added

...

...

...

Image Removed

> SETUP

> PLUGINS

SETTINGS: WORKFLOW

It's where you find most of the stuff related to author guidelines and the review phase, but also about submission settings (e.g. confirmation statement component).

*Eli's note for the 2025 team, most interesting:

Review forms are in SETTINGS: WORKFLOW > REVIEW (upper tab) > REVIEW FORMS (left tab). Once a review form has been used to review by any user, it cannot be edited anymore! 

There may be a way to set automatic reminders in SETTINGS: WORKFLOW > REVIEW (upper tab) > SETUP (left tab)

...

We can set and change friendlier and more customized templates for emails and reminders that can be sent automatically within the system: https://journals.phl.univie.ac.at/meicogsci/management/settings/manageEmails

SETTINGS: USERS & ROLES

You can browse specific users in the first upper tab, and see the role possibilities in the second.

Permissions are divided in four categories or stages: 

Submission

Review

Copyediting

Production

All roles are a combination of these categories or stages (which for our purposes, is not most helpful).

There are currently 17 roles, and any given user can have multiple roles assigned. Each role has an associated permission level.

Permission levels are:

...

Assistant

...

SUBMISSIONS

It's where you can see and do everything related to the particular submissions of the author abstracts and reviews.

ISSUES

Mostly relevant just before the last step for publishing the issue (June), to rearrange what you see here:

Image Removed

...

Edit the configuration of an issue (name, date of publication, volume - formal number).

Add a cover image and some text about this issue.

...

Order the abstracts within each section in the right order.

In 2024, by author surname, manually once an issue is created and after all submissions have been assigned.

...

Order the sections.

In 2024, the order set is:

  • Editorial 
  • Plenary Talks
  • Workshops
  • Poster Abstracts
  • Talk Abstracts

...













-Right Sidebar elements in the homepage (Language Toggle Block: "Deutsch, English", Information Block "For Readers, For Authors, For Librarians", Developed By Block "Open Journal Systems" and a Subscription Block that actually doesn't appear, right?)SETTINGS: WEBSITE (on the left bar) > APPEARANCE (upper tab) > SETUP (left-central tab inside) > Scroll to the bottom.


Eli's note:

Beware there are two sections called "Setup". In the picture we are in SETTINGS: WEBSITE (left bar) > APPEARANCE (tab in the upper part) > SETUP (tab inside appearance, on the lef-central part) > "Logo".

Image Added

> SETUP

> PLUGINS

SETTINGS: WORKFLOW

It's where you find most of the stuff related to author guidelines and the review phase, but also about submission settings (e.g. confirmation statement component).

*Eli's note for the 2025 team, most interesting:

Review forms are in SETTINGS: WORKFLOW > REVIEW (upper tab) > REVIEW FORMS (left tab). Once a review form has been used to review by any user, it cannot be edited anymore! 


There may be a way to set automatic reminders in SETTINGS: WORKFLOW > REVIEW (upper tab) > SETUP (left tab)

  • Send an email reminder if a reviewer has not responded to a review request this manydays after the response due date.
  • Send an email reminder if a reviewer has not submitted a recommendation within this many days after the review's due date.


We can set and change friendlier and more customized templates for emails and reminders that can be sent automatically within the system: https://journals.phl.univie.ac.at/meicogsci/management/settings/manageEmails


SETTINGS: USERS & ROLES

You can browse specific users in the first upper tab, and see the role possibilities in the second.


Permissions are divided in four categories or stages: 

Submission

Review

Copyediting

Production

All roles are a combination of these categories or stages (which for our purposes, is not most helpful).

There are currently 17 roles, and any given user can have multiple roles assigned. Each role has an associated permission level.

Permission levels are:

Journal Manager
Section Editor

Assistant

Author
Reviewer
Reader
Subscription Manager

SUBMISSIONS

It's where you can see and do everything related to the particular submissions of the author abstracts and reviews.


ISSUES

Mostly relevant just before the last step for publishing the issue (June), to rearrange what you see here:

Image Added

WhatWhere (in the dashboard)

Edit the configuration of an issue (name, date of publication, volume - formal number).

Add a cover image and some text about this issue.

ISSUES > Back Issues or Future Issues tab, click on your issue > "Issue Data" tab

Order the abstracts within each section in the right order.

In 2024, by author surname, manually once an issue is created and after all submissions have been assigned.

ISSUES > Back Issues or Future Issues tab, click on your issue > "Table of Contents" tab > upper right button "Order"

Order the sections.

In 2024, the order set is:

  • Editorial 
  • Plenary Talks
  • Workshops
  • Poster Abstracts
  • Talk Abstracts
ISSUES > Back Issues or Future Issues tab, click on your issue > "Table of Contents" tab > upper right button "Order"

Image AddedImage AddedImage Added


Eli's note for team 2025:

It's worth noticing the actual issue ID in the URL is not the same as the formal number "Identification Volume". E.g. 

And the ID in the URL changes every time the issue is unpublished and published again (be wary of this).


ANNOUNCEMENTS

Add or modify the announcements / posts that appear in the website.


STATISTICS

About the number of users, editorial activity etc. Mostly exportable in CSV format (and from there to Excel).

Interestingly:
-Most visited articles
https://journals.phl.univie.ac.at/meicogsci/stats/publications/publications 

Image Added





Activity Log

16.07.2024

Elisabet, @Elisabeth, @Evelyn, @Odin

  •  Meeting and sharing content with the Bratislava team (@Martin & @Kika).

15.07.2024

Elisabet Delgado Mas Evelyn Fischer

  •  Backend documentation on OJS web scrapping, and link to scripts.
  •  Create queries that:
    •  Given submission_id, provides the backend and frontend links of its submission.
    •  Given one of the user's author_id, show their email and both publications.
    •  Given one of the user's author_id, show their data (familyName, givenName, affiliation, country) for both publications

Image RemovedImage RemovedImage Removed

Eli's note for team 2025:

It's worth noticing the actual issue ID in the URL is not the same as the formal number "Identification Volume". E.g. 

And the ID in the URL changes every time the issue is unpublished and published again (be wary of this).

ANNOUNCEMENTS

Add or modify the announcements / posts that appear in the website.

STATISTICS

About the number of users, editorial activity etc. Mostly exportable in CSV format (and from there to Excel).

Interestingly:
-Most visited articles
https://journals.phl.univie.ac.at/meicogsci/stats/publications/publications 

Image Removed

Activity Log

16.07.2024

Elisabet, @Elisabeth, @Evelyn, @Odin

  •  Meeting and sharing content with the Bratislava team (@Martin & @Kika).

15.07.2024

Elisabet Delgado Mas

  •  General structure and order.
  •  Backend documentation on OJS web scrapping.

09.07.2024

Elisabet Delgado Mas

  •  Backend documentation on OJS exports.

02.07.2024

Elisabet Delgado Mas

  •  Frontend documentation on OJS.

27.03.2024

Elisabet Delgado Mas

  • Goal: Explore database, create table documentation, get first scripts.
    •  Elisabet Delgado Mas Create table documentation.
    •  Elisabet Delgado Mas Create queries that:
      •  Given submission_id, provides the backend and frontend links of its submission.
      •  Given one of the user's author_id, show their email and both publications.
      •  Given one of the user's author_id, show their data (familyName, givenName, affiliation, country) for both publications.
      •  Give list of users with a given permission.
    •  Elisabet Delgado Mas Create script that gets authors and submissions.

19.03.2024

Elisabet Delgado Mas Evelyn Fischer

12.03.2024

Elisabet Delgado Mas Evelyn Fischer

...

    • .