Eligibility criteria tags support conditions with 'AND' only and not 'OR'

[nirmalnr]

For example current tag structure supports the following:

• User must have 60% in 10th
• User must have 60% in 12th
  Here the user must have above 60% in both 10th and 12th

It does not support the below:

• User must have minimum 60% marks in undergraduate or postgraduate studies

[santhosh-7777]

@nirmalnr i would like to work on this issue could u assign this to me?

[Abhishek1106kr]

@nirmalnr Thank you for raising this important issue. I've analyzed the current tag structure in the ONEST-Specification repository, and I completely understand the limitation where eligibility criteria tags only support 'AND' conditions and not 'OR' conditions.

Current Problem

As described in the issue, the current academic-eligibility tag group (in work-opportunities/recommended_tags.md) uses separate tag groups for each condition, which implicitly creates an 'AND' relationship between them. For example:

• User must have 60% in 10th
• User must have 60% in 12th

This means both conditions must be satisfied. However, there is no way to express:

• User must have minimum 60% marks in undergraduate OR postgraduate studies

Proposed Solution

I propose introducing a condition-type tag within each academic-eligibility tag group that explicitly specifies the logical relationship between multiple eligibility criteria. This would allow both 'AND' and 'OR' conditions to be expressed.

Solution 1: Add condition-type Tag to Academic Eligibility

Add a new tag field condition-type with values "AND" or "OR" to the academic-eligibility tag group. This tag would indicate how multiple eligibility tag groups should be combined.

Updated Tag Table:

Tag code	Tag name	Tag value	Description
condition-type	Condition Type	"AND", "OR"	Specifies the logical relationship between multiple eligibility criteria. Default is "AND" if not specified.

Example: OR condition for undergraduate OR postgraduate

{
  "tags": [
    {
      "display": true,
      "descriptor": {
        "code": "academic-eligibility",
        "name": "Academic eligibility"
      },
      "list": [
        {
          "descriptor": {
            "code": "course-level",
            "name": "Level of the course"
          },
          "value": "Under Graduate",
          "display": true
        },
        {
          "descriptor": {
            "code": "min-percentage",
            "name": "Minimum percentage"
          },
          "value": "60",
          "display": true
        },
        {
          "descriptor": {
            "code": "condition-type",
            "name": "Condition Type"
          },
          "value": "OR",
          "display": false
        }
      ]
    },
    {
      "display": true,
      "descriptor": {
        "code": "academic-eligibility",
        "name": "Academic eligibility"
      },
      "list": [
        {
          "descriptor": {
            "code": "course-level",
            "name": "Level of the course"
          },
          "value": "Post Graduate",
          "display": true
        },
        {
          "descriptor": {
            "code": "min-percentage",
            "name": "Minimum percentage"
          },
          "value": "60",
          "display": true
        },
        {
          "descriptor": {
            "code": "condition-type",
            "name": "Condition Type"
          },
          "value": "OR",
          "display": false
        }
      ]
    }
  ]
}

This means the candidate must satisfy either the undergraduate criteria OR the postgraduate criteria.

Solution 2: Add group-logic Field at TagGroup Level

Alternatively, introduce a group-logic field at the parent TagGroup level (outside the list array) to define the relationship between sibling tag groups with the same code.

{
  "display": true,
  "descriptor": {
    "code": "academic-eligibility",
    "name": "Academic eligibility"
  },
  "group-logic": "OR",
  "list": [
    {
      "descriptor": {
        "code": "course-level",
        "name": "Level of the course"
      },
      "value": "Under Graduate",
      "display": true
    },
    {
      "descriptor": {
        "code": "min-percentage",
        "name": "Minimum percentage"
      },
      "value": "60",
      "display": true
    }
  ]
}

Implementation Steps

I'd like to work on this issue and will be implementing the changes in the following files:

1. docs/implementation_guides/work-opportunities/recommended_tags.md - Add condition-type tag documentation with examples
2. docs/implementation_guides/learning-experiences/recommended_tags.md - Similarly update if needed for learning experiences domain
3. docs/implementation_guide.md - Update the overall implementation guide to reflect the new condition-type semantics
4. specs folder - If there are schema definitions, update them to include the condition-type field

Files I Plan to Modify in My Fork

I have already forked this repository at Abhishek1106kr/ONEST-Specification. I will:

1. Create a new branch fix/issue-17-eligibility-or-support
2. Add the condition-type tag to the academic-eligibility tag group
3. Update all relevant documentation with clear examples for both AND and OR conditions
4. Add a new section in the implementation guide explaining how BAPs and BPPs should interpret these conditions

@nirmalnr Could you please assign this issue to me so I can start working on it? I believe this enhancement will significantly improve the flexibility of eligibility criteria in the ONEST network and make it more aligned with real-world scenarios where candidates may qualify through multiple pathways.