[20200320_184315 UTC: Update: Made the dept. line longer to better demonstrate space [un]availability.--martyb]
[20200320_202305 UTC: Update: Added topics: "/dev/random", "Code", "Software", and "Answers" topics to better illustrate their use of space in a story. --martyb]
[20200321_175412 UTC: Update: superseded by: Skip to comment(s) -- Second Try --martyb]
First: Please accept my best wishes to everyone during SARS-CoV-2 / COVID-19 / Coronavirus pandemic. Please take all necessary precautions to keep yourself and those around you safe!
Second: I should not have been surprised, but I must confess my admiration at how the SoylentNews community came together in support of each other in response to SoylentNews Community -- How has SAR-CoV-2 (Coronavirus) / COVID-19 Affected You? As of my writing this, there are over 300 comments! community++ This is what I had hoped for when SoylentNews started over six years (Wow!) ago, and so validates my giving of my time to this site!
Third: (and the focus of this story) our virus roundup stories are... long. An AC posted a comment: thanks to eds:
Thanks editors for pulling together this summary. SN for the win!One comment--it is kind of long to scroll down through, to get to the comments. Perhaps next time some of the longer stories could be put inside the spoiler tag?"
Thanks editors for pulling together this summary. SN for the win!
One comment--it is kind of long to scroll down through, to get to the comments. Perhaps next time some of the longer stories could be put inside the spoiler tag?"
This was quickly acted on by a member of staff, but that was not universally embraced as a "Good Idea". Both Soylentils, to my eye, had good points. If I am visiting an active story again, I have already read the story (both the "Intro Copy" and the "Extended Copy"). Why should I have to scroll through a wall-of-text to get to the comments? The suggestion of using <spoiler>...</spoiler> to bracket the contents of each of the merged stories seemed like a reasonable suggestion. But, when you have a hammer... Right idea, but maybe not quite the right tool.
Aside: If I am reading a review of, say, a movie, then a spoiler is an appropriate way to hide plot details from those who have not yet seen the movie. That is not the situation here. Why hide details of a story about the pandemic? Hmm. A good first try, perhaps, but it looks like we need something different in this case.
Idea: what if there were, say, a button at the top of the story that I could click and be brought immediately to the comment section of a story? Hey! I can do that!
Acknowledgements: At this point, I hereby express my sincere thanks to AndyTheAbsurd for constructing some CSS which allowed the conditional display of a button, and to FatPhil for his testing efforts. Thanks guys!
Read on past the break for details on the implementation and a request for assistance before I attempt to roll it out to production.
So, I hacked up something that I hope addressed the initial concern: "kind of long to scroll down through". I'll be the first to admit the implementation is crude. We can go for pretty later. (The perfect is the enemy of good enough, right?) I think the ideal would be to have a separate nexus for virus-related stories. That way we would not feel compelled to gather a bunch of story submissions into a single story. We could process each submission independently and release each on its own. Unfortunately, there is much more to it than just adding an entry to the site DB.
It has been implemented on our development server: https://dev.soylentnews.org/ and I hereby solicit feedback from the community on how well it works. It was implemented with one addition to an in-memory copy of a single site template (dispStory;misc;default).
For the curious, see Original and Updated Versions of Template: "dispStory;misc;default" ("Skip to Comment(s)" button), but do be aware that rehash replaced tabs with spaces, so what you see is NOT an exact copy of the sources.
Now what? Feedback! This is your site. I am well aware there are Soylentils who have a much better grasp of HTML and CSS than I do, and am hereby soliciting supportive feedback.
Which of the preceding homepage settings would be better served with just a simple anchor?
<a href="@acomments">Skip to Comment(s)</a>
First, being lead author isn't that uncommon, especially if they are PI on a grant. Some insist on being first because they are the ones sticking their neck out for students. Others, like myself, put the students first if they did the most work or to give them a boost in the indexes (it counts in my PoP quota regardless). It is a decision that correlates with age on a "U" shaped curve.
Second, document the crap out of everything. It will keep him from coming back at you later with various accusations about your non-compliance. Especially if you need to escalate things up your chain. Every time anyone says something in person that could affect you professionally, send an email with "based on our conversation today, it is my understanding that you [blah blah blah]. Let me know if I missed anything." and then save it, headers and all.
Third, this isn't fabrication of results, yet. It doesn't sound like you have actual proof that the numbers were off purposefully (although the PI may be realizing they messed up). Instead, put in black and white in an email exactly what you need to make things work according to your decision-making model. Provide all the information they need up to the Execution/Take-Action step. If you don't get what you need back, push it once in response and then pursue it to the student's union or student research office for vague advice (in person, you don't want to document something they could rat to your PI). They should be able to give you some more specific advice without starting informal procedures. If you are real hesitant, you may want to contact them first. I would definitely avoid mentioning it in the department because they are more likely to take the PI's side or tell him (unless they really don't like him).