After reading the literature, decide where to return
The important thing after reading a paper is not to stop because it was interesting. Here, we will divide the document into four paths depending on where it will be returned and used, and then pin the next page.
Four paths to follow after literature
| What you want to do next after looking at the literature | Next page | What to decide there |
|---|---|---|
| I want to return to the unresolved problem map | Research Harvest | I will organize which literature is effective for U and what is still unresolved. |
| I want to connect to proposals and implementation policies | Proposals | Check which stream or proposal the literature supports. |
| I want to shift to work that can be done right here and now | Issue | Organize executable changes, achievement conditions, disproval conditions, and presence or absence of external dependencies. |
| I want to turn it into a preparation for external collaboration or joint research | Collaborations | Check which collaboration candidates and preparations the document works with. |
Why this division
| way | Reasons for going to the page after reading the literature |
|---|---|
| Organize unresolved issues | The purpose of reading literature is to first update "which problems have been solved and to what extent." |
| Proposal organization | This is because there are cases where you want to directly link knowledge from the literature to proposals and implementation policies. |
| Issue conversion | If you don't reduce it to tasks that can be done right here and now, it's easy for your notes to be scattered as literature notes. |
| Cooperation preparation | Even if external collaboration is required, we can first prepare in-house preparations based on literature. |
Assistance wiki when you stop midway
| Place to stop | Go back to wiki |
|---|---|
| Stop at the difference between a collection of papers and a literature map | How to read the literature and evidence page |
| Stop at U number | U number guide |
| Stops due to difference between Scopus, arXiv, and source_logged | How to read document source type and status labels |
| Stop at suggestion state label | How to read proposals and status labels |
| Stops due to difference between issue and collaboration candidate | In-house production and external dependencies |
Common ways to get lost
Mistake
- Finding an interesting paper and leaving it as a note: It's better to decide which public page to return to so it won't get cluttered.
- The publication of a collection of papers alone is read as the central rationale: Connections to open questions and proposals must be confirmed.
- Regarding it as implemented just by returning to the proposal page: Proposals are organized, issues and deliverables are different.
- Go to collaboration candidates and skip in-house preparations: It is easier to proceed if you solidify the required specifications and minimum deliverables first.
Where to return next
If you want to go back to the role differences of the entire literature page, please use How to read the literature and evidence page, if you want to go back to the map of unresolved issues, please use Literature map, and if you want to go back to work that can be done right here and now, please use Contribution guide.