Answers.Body: <p>As @Demerit says, the best option for a particular task depends on the specifics.</p>
  <p>More generally, one key difference is that SearchKit is part of core (core extension) whereas DataProcessor is a third-party extension.  SearchKit is developing rapidly and very closely linked to APIv4.  It will eventually replace much of the existing core UI and work is underway on that - see for example recent  changes to deduping and the AdminUI extension.</p>
  <p>DataProcessor is also very capable but I don't see it ever being adopted within core.</p>
  <p>You're asking where to invest your time: my choice is SearchKit first.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-03-01T09:51:46.373Z
Answers.Text: Right, that's what I thought, thank you.
Answers.UserDisplayName: yurg
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-03-01T09:09:46.513Z
Answers.LastActivityDate: 2023-03-01T09:09:46.513Z
Answers.UserDisplayName: Aidan
Body: <p>Which one to go? Both doing the same job, SearchKit is like a favourite kid. None satisfies my small task on 100% so which one to invest the time to, per your opinion?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-02-28T21:23:59.827Z
Comments.Text: Can't really answer this without having some idea what the task is. Depending on what it is there might even be a third option that's better.
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-02-28T21:56:44.947Z
Comments.Text: Frontend visual search form with actions (print pdf) and filters (participants by event title), which displays name, address and  membership types in a 3x3 grid.
Comments.UserDisplayName: yurg
Tags: <searchkit><data-processor>
Title: DataProcessor vs SearchKit?
ThreadText: # DataProcessor vs SearchKit?
  
  (Asked by: username_0 on 2023-02-28)
  
  Which one to go? Both doing the same job, SearchKit is like a favourite kid. None satisfies my small task on 100% so which one to invest the time to, per your opinion?
  
  **Tags:** searchkit, data-processor
  
  > **Comments:**
  > **username_1**: Can't really answer this without having some idea what the task is. Depending on what it is there might even be a third option that's better.  
  > **username_0**: Frontend visual search form with actions (print pdf) and filters (participants by event title), which displays name, address and  membership types in a 3x3 grid.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2023-03-01. Score: 3 | Accepted answer
  
  As @username_1 says, the best option for a particular task depends on the specifics.
  
  More generally, one key difference is that SearchKit is part of core (core extension) whereas DataProcessor is a third-party extension. SearchKit is developing rapidly and very closely linked to APIv4. It will eventually replace much of the existing core UI and work is underway on that - see for example recent changes to deduping and the AdminUI extension.
  
  DataProcessor is also very capable but I don't see it ever being adopted within core.
  
  You're asking where to invest your time: my choice is SearchKit first.
  
  > **Comments:**
  > **username_0**: Right, that's what I thought, thank you.  
  
  ---
  
  