Difference between revisions of "Template:Latest news"

From LIMSWiki
Jump to navigationJump to search
(Removed April 30 news due to space constraints.)
 
(50 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<h2 style="font-size:105%; font-weight:bold; text-align:left; color:#000; padding:0.2em 0.4em; width:50%;">August 25, 2014:</h2>
<h2 style="font-size:105%; font-weight:bold; text-align:left; color:#000; padding:0.2em 0.4em; width:50%;">November 20, 2023:</h2>
[[File:Information overload1.jpg|left|180px]]'''Have you ever experienced information overload?''' Maybe you were like the person in this image at one point, baffled by too many choices and not enough organization. Yet as society continues its march towards further digitizing and storing content and data, finding exactly the information you want becomes increasingly daunting. Organizing and presenting large amounts of information well is now a desirable trait, whether it's a programmer developing a user interface and query tools for [[laboratory informatics]] software or a teacher creating an online course using a learning management program like [[Moodle]].
[[File:Fig3 Liscouski SciStudGuideLabInfo23.png|left|180px]] '''Are you studying some sort of [[laboratory]]-based science in university?''' How well do your classes address [[laboratory informatics]] topics, particularly in the scope of industrial labs and how they operate outside of academia? If you find the discussion lacking, then his guide by industry veteran Joe Liscouski will be worth a look. In his guide ''[[LII:A Science Student's Guide to Laboratory Informatics|A Science Student's Guide to Laboratory Informatics]]'', Liscouski presents "an annotated map of the laboratory portion of a technological world, identifying critical points of interest and how they relate to one another, while making recommendations for the reader to learn more." Hope you find it useful! [[User:Shawndouglas|Shawn Douglas]] ([[User talk:Shawndouglas|talk]]) 18:48, 20 November 2023 (UTC)


We've also tried to be cognizant of this problem when determining how to present information in this wiki. The front page has evolved to better and more appealingly organize data access into little "portals" or jumping-off points. But even that becomes increasingly daunting as wiki content continues to be added. This requires a more thoughtful approach using built-in and third-party tools for the wiki software. One recent attempt to organize information involves the use of [[MediaWiki]]'s category tags to better effect. I personally create 18 broad categories that all or most of our non-vendor wiki content falls under. The results of that effort can be found at the '''[[LIMSWiki:Glossary]]''' page. Some may find those categorizations too broad; however, articles can have more than one category. I want to use these 18 categories (with the potential for more later) to cover the entire non-vendor article base. Additional category tags can be applied to further granulate those categories, including crossover. For example, [[electronic data interchange]] may be categorized under the glossary category "Software and hardware terms" and [[hospital information system]] under "Software systems," yet both share the category tag "Health informatics."
<br />&nbsp;<br />


Another attempt to organize this wiki's content is via the MediaWiki [https://www.mediawiki.org/wiki/Extension:Collection Collection] extension. This allows users to render wiki content into a digital book-like structure. We have a live example with the '''[[LIMSWiki:Publications|The Complete Guide to LIMS & Lab Informatics]]'''. The upside is a user can learn about a topic from a curated collection of wiki content. The downside is the content is static, meaning like traditional published documents a new copy must be made to contain updated content. However, we've included live links to the contained articles on the wiki page.
<h2 style="font-size:105%; font-weight:bold; text-align:left; color:#000; padding:0.2em 0.4em; width:50%;">July 26, 2023:</h2>
[[File:Man and Woman Shaking Hands.jpg|left|180px]] '''Do you feel your lab needs [[laboratory informatics]] software but you're not sure how to justify it to management?''' Then [[LII:Justifying_LIMS_Acquisition_and_Deployment_within_Your_Organization|this new guide]] from Joe Liscouski and Shawn Douglas may be just what you need. Justification for a [[laboratory information management system]] (LIMS) or some other lab management solution isn't always straightforward with upper management and critical stakeholders; the process will need to be succinct and relevant, based on organizational goals, economic concerns, and practical realities. This guide will help you—whether you are a lab manager, lab technician, or someone else in the organization with a stake in seeing [[laboratory]] operations improve—understand what a LIMS is, what the alternatives are, what and why acquiring one looks like, and what needs to be considered in putting together a competent and persuasive LIMS project proposal. This guide also includes a handy Microsoft Excel workbook that will help act as a "cheat sheet" for persuading stakeholders to better buy into your vision of LIMS acquisition and deployment within your organization. Enjoy! [[User:Shawndouglas|Shawn Douglas]] ([[User talk:Shawndouglas|talk]]) 16:32, 26 July 2023 (UTC)


As we continue our efforts to add more content, we're hoping tools like the glossary and Collection continue to make approaching the wiki's content less intimidating, alleviating the worries of information overload. We'll also continue to evaluate the front page and how it can be used to better make content easier to find.
[[User:Shawndouglas|Shawn Douglas]] ([[User talk:Shawndouglas|talk]]) 12:53, 25 August 2014 (EDT)
<br />
<br />

Latest revision as of 16:37, 19 February 2024

November 20, 2023:

Fig3 Liscouski SciStudGuideLabInfo23.png

Are you studying some sort of laboratory-based science in university? How well do your classes address laboratory informatics topics, particularly in the scope of industrial labs and how they operate outside of academia? If you find the discussion lacking, then his guide by industry veteran Joe Liscouski will be worth a look. In his guide A Science Student's Guide to Laboratory Informatics, Liscouski presents "an annotated map of the laboratory portion of a technological world, identifying critical points of interest and how they relate to one another, while making recommendations for the reader to learn more." Hope you find it useful! Shawn Douglas (talk) 18:48, 20 November 2023 (UTC)


 

July 26, 2023:

Man and Woman Shaking Hands.jpg

Do you feel your lab needs laboratory informatics software but you're not sure how to justify it to management? Then this new guide from Joe Liscouski and Shawn Douglas may be just what you need. Justification for a laboratory information management system (LIMS) or some other lab management solution isn't always straightforward with upper management and critical stakeholders; the process will need to be succinct and relevant, based on organizational goals, economic concerns, and practical realities. This guide will help you—whether you are a lab manager, lab technician, or someone else in the organization with a stake in seeing laboratory operations improve—understand what a LIMS is, what the alternatives are, what and why acquiring one looks like, and what needs to be considered in putting together a competent and persuasive LIMS project proposal. This guide also includes a handy Microsoft Excel workbook that will help act as a "cheat sheet" for persuading stakeholders to better buy into your vision of LIMS acquisition and deployment within your organization. Enjoy! Shawn Douglas (talk) 16:32, 26 July 2023 (UTC)