About ojs db tables

woosik.K · May 1, 2019, 3:30pm

Hi
I read a document about ojs DB table.
But I don’t understand access_keys & auth_source & custom_issue_orders & custom_section_orders & data_object_tombstone_oai_set_objects & data_object_tombstone_settings & data_object_tombstones & institutional_subscriptions & institutional_subscription_ip & metadata_description_settings & metadata_descriptions & oai_resumption_tokens & queries & query_participants & rt_contexts & rt_searches & rt_versions at the ojs3 DB table.
Can I get a little more detailed explanation?

ctgraham · May 2, 2019, 11:44am

We have not yet consolidated this kind of developer information to a Technical Reference for OJS/OMP 3.x. Some brief description for some of these tables is present in the OJS 2.x technical reference:

You can also find descriptions of the tables in the XML schema descriptions:

github.com

pkp/pkp-lib/blob/d79f9832c3a7e00450631b0e1cad9bfa9f137365/xml/schema/common.xml#L303-L327


	<table name="access_keys">
		<field name="access_key_id" type="I8">
			<KEY />
			<AUTOINCREMENT />
		</field>
		<field name="context" type="C2" size="40">
			<NOTNULL/>
		</field>
		<field name="key_hash" type="C2" size="40">
			<NOTNULL/>
		</field>
		<field name="user_id" type="I8">
			<NOTNULL/>
		</field>
		<field name="assoc_id" type="I8"/>
		<field name="expiry_date" type="T">
			<NOTNULL/>
		</field>
		<descr>Access keys are used to provide pseudo-login functionality for security-minimal tasks. Passkeys can be emailed directly to users, who can use them for a limited time in lieu of standard username and password.</descr>
		<index name="access_keys_hash">

This file has been truncated. show original

github.com

pkp/pkp-lib/blob/d79f9832c3a7e00450631b0e1cad9bfa9f137365/xml/schema/common.xml#L137-L159


	<!--
	  *
	  * TABLE auth_sources
	  *
	  -->
	<table name="auth_sources">
		<field name="auth_id" type="I8">
			<KEY />
			<AUTOINCREMENT />
		</field>
		<field name="title" type="C2" size="60">
			<NOTNULL/>
		</field>
		<field name="plugin" type="C2" size="32">
			<NOTNULL/>
		</field>
		<field name="auth_default" type="I1">
			<NOTNULL/>
			<DEFAULT VALUE="0"/>
		</field>

This file has been truncated. show original

github.com

pkp/ojs/blob/642655d40237011a16b061b498c7d0f817276a94/dbscripts/xml/ojs_schema.xml#L351-L371


	<!--
	  * TABLE custom_issue_orders
	  *
	  -->
	<table name="custom_issue_orders">
		<field name="issue_id" type="I8">
			<NOTNULL />
		</field>
		<field name="journal_id" type="I8">
			<NOTNULL/>
		</field>
		<field name="seq" type="F">
			<NOTNULL/>
			<DEFAULT VALUE="0"/>
		</field>
		<descr>Custom sequencing information for journal issues, when available</descr>
		<index name="custom_issue_orders_pkey">
			<col>issue_id</col>
			<UNIQUE/>
		</index>
	</table>

Are you looking to do reporting by direct SQL queries? If so, what kind of reporting are you trying to accomplish?