methnen

Andrea Landonio

sburdett

bheadrick

CloudSearch is a flexible plugin that allows you to leverage the search index power of Amazon CloudSearch in your WordPress site. 
To use this plugin you’ll need an Amazon Web Services account. Attention: Amazon CloudSearch is a paid service and will require a credit card.
Before you can start using CloudSearch, the plugin needs to be activated and configured. Activate the plugin, then go to the menu “CloudSearch -> Settings” (you can find this menu in the sidebar of your WordPress admin panel). 
Fill the form data:
<ul>
<li>Enter Amazon access key ID, Amazon secret access key and Amazon region for your account (look for “Security Credentials” in your Amazon console to retrieve these data)</li>
<li>Enter your CloudSearch index search endpoint and the domain name (I suggest to create the CloudSearch index before you start the plugin configuration)</li>
<li>Schema settings</li>
<li>Other settings</li>
</ul>
IMPORTANT NOTES WITH RELEASE 2.0.0: 
* At least WordPress 4.4 version mandatory (for WP_Term support) 
* Changed APIs output from an array of IDs to an array of object composed by the entity ID and the entity type
Minimum requirements:
<ul>
<li>WordPress Version 4.4</li>
<li>PHP Version 5.3</li>
<li>Amazon Web Services account with CloudSearch enabled</li>
</ul>
<h4>Usage</h4>
<ol>
<li>Go to <code>CloudSearch -> Settings</code></li>
<li>Enter your <code>Amazon access key ID</code>, <code>Secret access key</code> and the <code>Amazon region</code> where you have created the CloudSearch index</li>
<li>Enter a <code>Search endpoint</code> and the <code>Domain name</code>. Get these info in your CloudSearch dashboard in AWS Console</li>
<li>Choose post types, custom fields and custom taxonomies that you want to export to the CloudSearch index</li>
<li>Set up other settings or leave defaults</li>
<li>Save settings.</li>
<li>Go to <code>CloudSearch -> Manage</code></li>
<li>Click the action <code>Create index</code>, <code>Run indexing</code> and <code>Sync all documents</code>. Between every action wait until the <code>Status</code> field is <code>Active</code>, then go on with the next task</li>
<li>After these operation your index is ready, now you can search documents in your CloudSearch index</li>
</ol>
Links: <a href="http://www.andrealandonio.it" rel="nofollow ugc">Author’s Site</a>

CloudSearch

This plugin works great and saved me a huge amount of time. The developer is also responsive and was quick to make improvements when I discovered an issue with the implementation.

Huge time saver and responsive developer

CloudSearch is a flexible plugin that allows you to leverage the search index power of Amazon CloudSearch in your WordPress site.

Evan Morgan

Citrus is a modern WordPress plugin that displays research publications beautifully on your website. Choose between automatic synchronization from the Pure API or manual entry of BibTeX data (paste or upload). Ideal for universities, research institutions, and academic departments.
Key features:
<ul>
<li>Flexible Data Sources: Use Pure API automatic sync OR manually provide BibTeX data (paste or upload)</li>
<li>Automatic synchronization from Pure API (schedule hourly, twice daily, or daily)</li>
<li>Manual BibTeX entry: Paste content directly or upload .txt files</li>
<li>Smart caching with WordPress transients to reduce API calls</li>
<li>Beautiful, responsive publication listings with search and filters</li>
<li>Multiple integration options: shortcode, Gutenberg block, and REST API</li>
<li>Optional AI-powered summaries (OpenAI-compatible) with 24-hour caching and rate limiting</li>
<li>6 color schemes + custom CSS support</li>
<li>Accessible, responsive design with dark mode</li>
<li>Secure options handling and nonce-protected REST endpoints</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>WordPress 5.8 or higher</li>
<li>PHP 7.4 or higher</li>
<li>For Pure API mode: Pure API version 5.24 (legacy versioned Web Service) access credentials (API key and organization ID)</li>
<li>For Manual Entry mode: BibTeX data from your reference manager (can be pasted or uploaded as .txt file)</li>
<li>(Optional) OpenAI-compatible API key for AI features</li>
</ul>
Note: Pure API mode is designed and tested with Pure API version 5.24, the final version of the legacy versioned Web Service. It may not be compatible with the new Pure API.
<h3>External Services</h3>
This plugin connects to external third-party services to provide its functionality. Below is detailed information about each service:
<h4>Pure API</h4>
What it is: Pure is a research information management system (RIMS) used by universities and research institutions to manage publication data. This plugin connects to your institution’s Pure API to retrieve publication metadata.
What it’s used for: Fetching and synchronizing research publication data (titles, authors, abstracts, publication years, etc.) from your institution’s Pure system to display on your WordPress site.
What data is sent: Your Pure API key and Organization ID are sent with each request to authenticate and specify which organizational unit’s publications to retrieve. No user data or visitor information is transmitted to Pure.
When data is sent: Data is sent when: 
– You test the API connection in the plugin settings 
– You manually trigger a sync via the admin dashboard or REST API 
– An automatic scheduled sync runs (hourly, twice daily, or daily, based on your settings)
Service provider: Your own institution’s Pure installation (self-hosted or managed by Elsevier)
Privacy and Terms: Please consult your institution’s Pure system administrator for information about data handling, privacy policies, and terms of use specific to your Pure installation.
<h4>OpenAI API (Optional)</h4>
What it is: OpenAI provides artificial intelligence models that can analyze and summarize text. This plugin optionally uses OpenAI-compatible APIs to generate summaries of research publications.
What it’s used for: Generating AI-powered summaries of selected publications when users click the “Generate AI Summary” button on the frontend.
What data is sent: Publication metadata (titles, abstracts, and years) of the selected publications is sent to the configured AI API endpoint (defaults to https://api.openai.com/v1/chat/completions). For 10 or fewer publications, full abstracts are sent. For more than 10 publications, only titles and years are sent. No visitor information or personal data is transmitted.
When data is sent: Data is only sent when: 
– A user explicitly clicks the “Generate AI Summary” button in the frontend 
– AI features are enabled in the plugin settings 
– The request hasn’t been cached (summaries are cached for 24 hours)
Service provider: OpenAI (default) or any OpenAI-compatible API service you configure
Terms and Privacy: 
– OpenAI Terms of Use: https://openai.com/policies/terms-of-use 
– OpenAI Privacy Policy: https://openai.com/policies/privacy-policy 
– If using an alternative OpenAI-compatible service, please consult that provider’s terms and privacy policy
Note: AI features are completely optional and disabled by default. The plugin works fully without AI integration.
<h3>Usage</h3>
<h4>Shortcode</h4>
Place on any page or post:
[citrus_publications]
With filters:
[citrus_publications author=”Smith” year=”2024″ limit=”10″]
Enable AI summary button:
[citrus_publications enable_ai_summary=”true”]
<h4>Gutenberg Block</h4>
Add the “Pure Publications” block and configure filters in the block settings.
<h4>REST API</h4>
<ul>
<li>Get publications (BibTeX): /wp-json/citrus/v1/publications</li>
<li>Get publications (JSON): /wp-json/citrus/v1/publications/json</li>
<li>Trigger sync (POST): /wp-json/citrus/v1/sync (requires authentication)</li>
</ul>

Citrus

Display research publications from Pure API or manually provided BibTeX data beautifully.

CloudSearch vs Citrus