This is a screenshot of how we were experimenting with ENCompass 2.0 shortly before our October user testing.  Note that the interface used tabs to introduce two components:  searching metadata about resources (Suggest a Resource) and browsing or searching for and within all types of resources (Browse/Search Resources).  Browse/Suggest a Resource allowed for searching both local and remote repositories.  On our Browse/Suggest a Resource screen, we included mostly categories linking to databases in our local repository.  These were databases that users could search by descriptive metadata within our system and then connect to for “native interface” searching.  We also included “A Direct Searching Connection,” a category for those remote repository connections we were able to configure. Resources under this category could be searched right down to the article level.  Although http, XML Gateway and Z39.50 connections were offered in 2.0, we found Z30.50 to be most reliable.
	[PAUSE]
	Our project team found this mixing of databases and journal articles in a federated search interface complicated and potentially confusing for our users.  While we knew users would welcome the ability to search down to the article level and select more than one database at once, we felt that this “mixed granularity” approach would create confusion.  We made some modifications before presenting to our October test users, as you will see…