(1) Learn the lingo:
Why? To help the user to better understand the context of their research interest, by supplying commonly associated terms in the literature (from titles and abstracts, potential to expand to semantic links in future?)
To do what? Use refined search terminology to find relevant research objects (articles, datasets, code, etc):
[MINIMAL] Subscribe to feed of objects (filter by type of content)
[DESIRED] Potential to include a collaborative annotation and snippet-notetaking application on top (e.g. hypothes.is) to enable researchers to collaborate with others as they explore the literature and to begin authoring review (respectively, not exclusive)
(2) Crack the community:
Why? To help the user to identify key researchers in the field, by displaying co-author networks related to the research object results from (1)
To do what?
[MINIMAL] Follow key researchers (further refine the search terms, keep on top of updates)
[MINIMAL] Identify researchers to connect with for collaboration (save to 'Future Friends')
[DESIRED] Ability to take notes about researchers (as a personal client relationship management tool)
(3) Find the field:
Why? To help user to understand key channels for sharing their work and connecting with peers
To do what?
[MINIMAL] Identify journals to publish in (e.g. include basic journal info (links), is it OA, how to submit (link), potentially include basic stats on reviewing time). Potential to link to authoring tools that enable direct submission to these journals (or at least show where this is available). Include preprint servers.
[MINIMAL] Identify conferences/meetings to attend (e.g. include basic conference info (with links): dates, location, submission deadline, registration deadline, fee, travel grants available)
[POTENTIAL EXTENSION] Community rating of journals - similar services at: http://www.journalysis.org/ and https://scirev.sc/ amongst other; also of conferences (is it worth my time/money to go there)?
(4) Other
Make it in such a way that integrations with other tools are easy, such integrations could be community-driven
Key differences to what we initially designed:
Overall, what this has that other search interfaces don't (WoS, MS Academic) is the focus on how the user can then use that information. I think that's important to focus on, hence making these user actions minimal requirements.
I think 'Find the Field' should be more about sharing work than finding literature, as literature searches are becoming more focussed on the article content than the journal it is in. This doesn't preclude including the option to add a journal to the search / generate a RSS feed for them. I've focussed on features here that help researchers to plan how they are going to communicate their work.
What do you think @martintoreilly @Nikoleta-v3 @geraintpalmer @BlairArchibald
(I need to do my own work now, but please do fire away, as I'd like to show this to my boss and discuss potential at some point)
Some potential refinements to the project idea:
(1) Learn the lingo: Why? To help the user to better understand the context of their research interest, by supplying commonly associated terms in the literature (from titles and abstracts, potential to expand to semantic links in future?) To do what? Use refined search terminology to find relevant research objects (articles, datasets, code, etc):
(2) Crack the community: Why? To help the user to identify key researchers in the field, by displaying co-author networks related to the research object results from (1) To do what?
(3) Find the field: Why? To help user to understand key channels for sharing their work and connecting with peers To do what?
(4) Other
Key differences to what we initially designed:
What do you think @martintoreilly @Nikoleta-v3 @geraintpalmer @BlairArchibald (I need to do my own work now, but please do fire away, as I'd like to show this to my boss and discuss potential at some point)