source-opuswatch contribution from SebasZwinkels

[SebasZwinkels]

What

This PR adds a new connector for source OPUSWatch (source-opuswatch).

Contributor-provided connector description:

Unlock Horticultural Insights with Airbyte and OPUSWatch

What is OPUSWatch?
OPUSWatch is a smart wearable solution developed by OPUS Solutions B.V., based in the Netherlands. This innovative smartwatch is specifically designed for the horticulture industry to digitize and streamline various operational processes within greenhouses and nurseries. It empowers growers to gain real-time insights into their labor, productivity, and overall operations. Employees use the OPUSWatch to easily record their tasks, track their work on specific crops, and even manage orders directly from their wrist. This data is then fed into a central system for analysis and decision-making.

Website: opuswatch.nl

What does the OPUSWatch Airbyte Connector do?
The Airbyte connector for OPUSWatch allows you to seamlessly extract valuable data from the OPUSWatch platform and load it into your data warehouse or lake. By connecting OPUSWatch to Airbyte, you can centralize your horticultural operational data with other business-critical information, enabling comprehensive analysis and reporting.

With the OPUSWatch Airbyte connector, you can retrieve the following streams of data:

• Clients: Information about your clients or customers.
• Locations: Details about the different locations or areas within your greenhouse or nursery.
• Rows: Data pertaining to the specific rows or sections where plants are cultivated.
• Users: Information about the individuals who have access to the OPUSWatch system.
• Workers: Details about your workforce, including their identification and potentially other relevant attributes.
• Worker Groups: Information about how your workers are organized into teams or groups.
• Tasks: Data on the various activities or jobs that are performed by workers.
• Task Groups: Information about how tasks are categorized or grouped together.
• Labels: Details about the different labels used for plants, products, or processes.
• Varieties: Information on the different plant varieties being cultivated.
• Registrations Initial: A snapshot of initial work registrations recorded by the OPUSWatch devices.
• Registrations Incremental: Updates and new work registrations recorded by the OPUSWatch devices since the last synchronization.
• Sessions Initial: A snapshot of initial work sessions or periods tracked by the OPUSWatch devices.
• Sessions Incremental: Updates and new work sessions or periods tracked by the OPUSWatch devices since the last synchronization.

By leveraging the OPUSWatch Airbyte connector, horticultural businesses can break down data silos and gain a holistic view of their operations. This enables data-driven decision-making for optimizing labor allocation, improving productivity, and ultimately enhancing the efficiency of their greenhouse or nursery operations.

The contributor provided the following description of the change:

Renamed the initial date-field to start_date AND adding better description of what OPUS is.

Details

Expand for list of spec properties and streams

Configuration

Input	Type	Description	Default Value
api_key	string	API Key.
start_date	string	Start Date.	20250101

Streams

Stream Name	Primary Key	Pagination	Supports Full Sync	Supports Incremental
client		No pagination	✅	❌
locations		No pagination	✅	❌
rows		No pagination	✅	❌
users		No pagination	✅	❌
workers		No pagination	✅	❌
worker groups		No pagination	✅	❌
tasks		No pagination	✅	❌
task groups		No pagination	✅	❌
labels		No pagination	✅	❌
varieties		No pagination	✅	❌
registrations initial		DefaultPaginator	✅	❌
registrations incremental		No pagination	✅	❌
sessions initial		DefaultPaginator	✅	❌
sessions incremental		No pagination	✅	❌

Reviewer checklist

• Consider how the connector handles pagination (docs).
• Help the contributor upload an icon that follows our icon design guidelines
• Click into the CI workflows that wait for a maintainer to run them, which should trigger CI runs

[CLAassistant]

All committers have signed the CLA.

[vercel]

@SebasZwinkels is attempting to deploy a commit to the Airbyte Growth Team on Vercel.

A member of the Team first needs to authorize it.

[marcosmarxm]

Some comments, it is missing the square svg icon as well.

[marcosmarxm]

Suggested change

	initial_data:
	start_date:

You can make this a datetime field and later apply a transformation to this specific format.

[marcosmarxm]

Can you provide a better description of what OPUS is? What is the website and API documentation?

[marcosmarxm]

@SebasZwinkels need you to sign the CLA to continue the review process.

[marcosmarxm]

@SebasZwinkels need you to sign the CLA to accept the contribution.

[SebasZwinkels]

Okay, I've made the following changes as requested:

• Signed the CLA.
• Added a square SVG icon.
• Updated the description of OPUS with more details, including the website.
• Changed the 'initial_data' field to 'start_date' in the manifest.yaml file.

Could you please confirm that these changes meet the requirements? I'm relatively new to contributing via Airbyte's pull request system, so I'd appreciate it if you could let me know if there are any other steps I need to take or if there's anything else I should be aware of. Thanks for your help!

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
airbyte-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 28, 2025 1:47pm

[marcosmarxm]

Congrats @SebasZwinkels awesome contribution!