EMS Matching Experience
-----------------------
Initially, using EMS was a frustrating experience. When used the correct way,
the system would behave as intended, but there were too many cases where
slight variations in the inputs would cause the whole system to not work (such
as having spaces in rules' names). Additionally, not being able to edit rules
was a major annoyance since it meant that anytime the user messed up, the
entire process of creating features, creating rules, etc would have to be
restarted. On the positive end, when debugging the evaluation screen was very
clear. The ability to sort on the tuples in the data set that were missed and
that were wrong was very useful in achieving high precision and recall. Color
coding the tuples also helped. Overall, the system will be very useful once
the bugs in every use case have been fixed.

Suggestions
-----------
1. Have first/previous/next/last on bottom of debug page as well as top

2. When viewing tables, let me change the size of everything. I need to change the width of columns, and especially remove that column about facets and filters on the left. If only need to read that information once.

3. Matcher Edit is important, and needs to be similar to the Matcher Add interface (list of rules that will be fired) rather than a string. I don’t remember what I called all my rules!

4. There needs to be unlimited number of rules in a matcher. Maybe there is some technical reason behind this, but to users it seems to be a problem with the frontend.

5. Allow more than 50 results per page. 200? 500? I personally would rather scroll than page through a bunch of results.

6. This may be complicated, but working with any date string should be supported in EMS. That is, if two different tables have different date strings, there should be simple functions which say “7 days of each other” or “same year”. The underlying code should understand this, but on it’s face, the output would still be the same, human readable code.

7. Delete table function does not work

8. Edits never worked for features/rules/matchers

9. Allow me to resize the debug output windows. I want to see more at once without having to scroll down the page.

10. I’m using this by creating rules, and testing those rules on the data to see how they do. Let me bypass the matcher stage, and debug on the fly with just a single rule that I’ve created, to see how it does.

11. Functions need more documentation. For example, what does EXACT_MATCH output when it’s true? Documentation does not tell me