Hey guys,
I've done some more work this weekend on the search results.
http://skitch.com/jdumay/6cc2/archiva-search-results-w-no-duplicates-repository-id-or-versions-displayed
So far:
* There are no duplicate entries.
* I've removed the link to the repository the result was from
(otherwise we might have two copies of "commons-lang" appearing in the
results but from different repositories. IMO, this information can be
found on the artifact info page).
* Removed the versions available.
* Clicking on the artifact link now takes you to browse the versions.
Thoughts?
James
On 05/12/2008, at 5:39 PM, Brett Porter wrote:
I visited James today and we came up with this list of things to fix
a bit more urgently (I'll be putting them in JIRA later).
Already changed:
* remove dependencies/filecontent from the quick search - must not
search for dependencies on commons-lang
* change the default search to AND instead of OR
Still to look at:
- [ ] improve the search results page
- [ ] remove metadata files
- [ ] merge versions in search results
- [ ] for snapshots, just show SNAPSHOT, not timestamps
- [ ] show hits in the results (this may not be possible or
needed with better results, however)
- [ ] existing JIRA complaints
- [ ] MRM-732 (tokenizing)
- [ ] MRM-495 (weighting)
- [ ] MRM-609 (windows bug - may be fixed)
- [ ] MRM-933 (hit count, pagination completely busted)
- [ ] advanced search
- [ ] improve appearance and flexibility, maybe change to
"add term" buttons on the default search
- [ ] class/package search is still flaky
- [ ] might be the analyzer rules, etc. for splitting on
'.'
- [ ] browse improvements
- [ ] artifact version list should show basic shared project
information rather than having to drill into one version
- [ ] snapshot should go to a page that shows a list of versions
(go to latest, but list previous snapshots)
Thoughts?
Cheers,
Brett
On 14/11/2008, at 11:40 AM, James William Dumay wrote:
Hey guys,
As mentioned on IRC we all agreed that our search feature is a
little suboptimal.
I would like to propose the following improvements:
* Search should be more like mvnrepository.com (showing codebase
growth etc).
* We should figure out a way of using up stream repository indexes
to improve search results.
* Advanced search needs a good rethink - we should probably use a
filter approach so that you could do bytecode: search results that
include free text search.
* UI improvements so that the user experience feels more intuitive.
Discuss!
James
--
Brett Porter
[email protected]
http://blogs.exist.com/bporter/
