I search jobs by filtering all available jobs, according to two kind of property sets:
- search properties: like the category
- job properties: like the number of proposals
If you used Upwork via the web interface, setting search properties corresponds to select a category and the filters about the budget, for example, while using job properties corresponds to discarding job offers which are too old, or with too many or too few interviewed candidates, for example
Turns out that these different property sets are distinct also in the Upwork Application Programming Interface. Thus it is natural that search properties and job properties are the main concepts around which this project is built.
$ opwer-search query | runhaskell my-filter.hs
This will search for jobs using search properties described in
query, and then filter them using my-filter.hs. query is a file
containing parameters corresponding to
these.
What is my-filter.hs? Read below
For the filtering part, since i do not want to invent a new language,
i thought that the most effective way is to just use Haskell. Opwer
provides a framework to generate a filtering script out of a pure
filtering function. This way, filtering conditions can be expressed in
a very flexible way. You don't like Haskell? Use any language to write
your filtering script. opwer-search will return one result per line,
so that any external script can parse them. Obviously, by writing the
script in Haskell one can reuse the types and the framework provided
by Opwer.
Note that this structure is not computationally efficient, because i am currently more concerned about flexibility than performances.
My assumption is that you will use the commands provided by Opwer
always from the same directory, where you will keep configuration
files for search and filtering scripts. Running opwer-init in that
directory will produce a file named opwer-credential, containing the
key provided from Upwork to you in order to use its services. This is
used by other Opwer scripts like opwer-search
This package depends on the
haskell-upwork and
web-output libraries. For
more info please open an issue