r12 - 17 Jul 2007 - 03:18:21 - LorenEveyYou are here: TWiki >  Archive Web > AtlasDemos > UrinarySystem4

The Urinary System


Description of the Urinary System

The series of organs in the urinary system function to produce, store, and eliminate soluble waste products from the body. The filtrates from the kidney are transported by the ureter to the bladder for storage, and are eliminated by way of the urethra. A major function of the system is to salvage water, sugars, and ions from the filtrate and return them to the blood. In addition, specialized structures within the kidney secrete the vasopressor renin, which increases systemic blood pressure.

The Kidney

* Renal Corpuscle

* Proximal Convoluted Tubule (PCT)

* Thin Tubules (Thin Ascending Loop of Henle)

* Distal Convoluted Tubule (DCT)

* Juxtaglomerular Apparatus

* Collecting Tubules

The Ureter

The Urinary Bladder

Review of The Urinary System

Review of Slides

Click on the thumbnail to begin a complete review of all urinary system slides.
b66_renal_cortex_10x_pas.jpg      
B66, PCT, 10x (PAS) .    

Summary of Identifications

Rowup Structure Abbreviation Optimal Stain Representative Section Note
1 Renal Corpuscle RC      
2 Cortex C      
3 Medullary Ray MR      
4 Arcuate Artery AA   B67, Thin Tubules, 2.5x Labeled (H&E) (1/4)  
5 Arcuate Vein AV   b67_arcuate_artery_kidney_2x_labeled.jpgB67, Thin Tubules, 2.5x (H&E)  
6 Collecting Tubules of Renal Medulla CT   B67, Thin Tubules, 40x Labeled (H&E) (4/4)  
7 Thin Limb (of Loop of Henle) TL   B67, Thin Tubules, 40x Labeled (H&E) (4/4)  
8 Thick Ascending (distal) Tubule TA   B67, Thin Tubules, 40x Labeled (H&E) (4/4)  
9 Proximal Convoluted Tubule PC   B68, PCT, 40x Labeled (PAS)  
10 Distal Convoluted Tubule DC   B68, PCT, 40x Labeled (PAS)  
11 Brush Border BB   B68, PCT, 40x Labeled (PAS)  
12 Bowman's Capsule (Parietal Layer) BC      
13 Bowman's Space BS      
14 Podocyte (visceral layer of Bowman's capsule) Pod      
15 Glomerulus (capillary tuft) G      
16 Vascular Pole VP      
17 Urinary Pole UP      

Back to LayoutVotingPage?

Comments

 
  • Speaking of the printable link. Try this "skin" in layer 5. You will notice that performance and readability is greatly enhanced as long as you navigate local links. Yet another argument for one chapter per topic page. One click on a outside link and the browser/server is apt to re-cache with a performance hit. Admittedly, the typical user is not going to appreciate printable viewing. Nevertheless, I am interested in implementing a "performance" skin. -- LorenEvey - 23 May 2007
  • Another argument for a chapter per page is to simplify printing. There are tools for generating a pdf document from a topic page. This could be very handy for those who want a hardcopy of the atlas. Further, for those who are annoyed by the left hand column and TWiki links, they can switch to the printable layout. This is advantageous to low resolution monitors. Admittedly, most people will not even notice the printable link at the top right but it is there and I frequently use it. -- LorenEvey - 23 May 2007
  • I agree that a child page is the way to do for an index or for information that applies across chapters. For example a glossary would be best in a child topic. Even here, an entire glossary can be in one topic page with targets. -- LorenEvey - 23 May 2007
  • Thoughts of how to avoid popups and extensive children/grandchildren guide my "playing" with layout five. To the user, a single topic page can be faster and more intuitive that a plethora of children and grandchildren. The images of a single page can be loaded in the background as a particular image is being studied. The server has time to cache predicted requests. Thoughtfully placed links within a page and "in-place" functions like navigable image galleries make a chapter/page solution tenable. The user would know whether they were at a local link or had linked out. Plus, tabbed browsing can be used and it works perfectly well with local links. At least it does in Firefox. Go to layout five and middle mouse click the TOC links. The result achieves much of the function of a popup but is a safer way to do it. For years, I have tried to show people how handy tabbed browsing is to Pubmed and Google searches. Some users just never get the hang of it. These same users will never be able to deal with a popup hidden behind a window. I get calls about this all of the time. Ultimately, if our headings and subheadings are carefully applied, a global TOC can be easily maintained. -- LorenEvey - 23 May 2007
  • Be ginger with popups. They are security problems. Users who have properly dealt with security issues to protect their identity will not view popups, myself included. I will not even use IE except when forced to do so for an update. Popup emulation by shelling out to new browser windows/tabs are a possiblity but cross platform and browser compatibility becomes an issue. Flyovers are dangerous enough. Java script is a security problem but we can not escape it. A primary burden I will inherit in administrating the infrastructure of this site will be assuring security and safe viewing. -- LorenEvey - 23 May 2007
  • Aha! Good call. There is still the possibility of a popup instead-- slide show in a popup and text still available. I have mixed feelings about popups. I see plenty of merit, but also annoyance, in them. -- AshleyLPistorio - 23 May 2007
  • Take a look at one of your child pages and notice the table. Then click a thumbnail. The table is gone. Put the table below the gallery and it remains in place without scrolling. Reversing the position of the gallery and table, though maybe disrupting the flow, increases the usability. In fact, once things settle, the edit button can be hidden and there can be two header rows. The top header row of a table could serve as a figure caption. I think that we need to make it so that these images do not appear so lonely and unguided. This is where the image plugin would shine but the authoring would be much more tedious. -- LorenEvey - 23 May 2007
  • I am all for eliminating arbitrary text. Worse than being arbitrary, this text betrays the heritage of the atlas as in 'in-house" document. I would rather the atlas appeared to be fresh. I still do not know what R-P XX is about. I imagine that is a reference to a textbook. I would like to see textbook references removed altogether. I already suggested this at the phone conference. I did not get very far. -- LorenEvey - 23 May 2007
  • Additionally, since we're linking right to the image within the table, for arbitrary topic names that have nothing to do with the labeled structure of reference, why not eliminate that, too? (e.g. "B67, 2.5x (H&E)" instead of how I have it now) For those slides that we use for multiple structures within the same table (not always the same image from that slide), we can give them "a", "b", etc. -- AshleyLPistorio - 23 May 2007
  • How about this way? It seems redundant to call it "labeled" since I would think it best to ONLY refer to labeled images for a table of this theme. Plus, the only 2.5x version of this slide image is labeled... so again, probably a waste of space. -- AshleyLPistorio - 23 May 2007
  • Regarding the image in the table. I like it. The image label in the table has merit so I would suggest creating an additional column for the representative image. For now, I would keep the note column. -- LorenEvey - 23 May 2007
  • Additionally, layout four was tailored toward the image gallery plugin. This plugin has strengths in navigation and placement, but weakness in annotation. The image plugin is much more powerful, but possibly much more difficult to work with. They key property of the image plugin is that you can wrap around text. Ultimately, this atlas may stand on its own as a textbook/atlas for medical histology. To that end, every image has to be annotated and justified for its existence. The image plugin will be best for this, but without extensive use of templates and forms, the development could be horrendous. Even if this atlas is to be solely ancilliary to a textbook, it still needs to stand on its own. In layer four I was working on a way to have guidance for every slide. Notice that the image gallery plugin consistently sets the top margin when viewing a single image. Thus, depending on the users screen resolution you can predict how much space is available below an image of a particular size. My screen is 1200 pixels high. I can view both an image of the current default size for the image gallery plugin and a table of identifications up to about 8 rows without scrolling. Thus, I can navigate an image gallery plugin gallery without scrolling and still be able to see the identifications. Try walking ISZ through a gallery over the phone with his 1084 high monitor and I think you will appreciate the merit of these considerations. ISZ often ignors the scroll bars. He is not alone. I suspect the 1200 pixel high monitors will become mainstream in a year or so. Further, many monitors rotate. The atlas would be maximally effective is viewed by a 1600X1200 monitor in portrait mode. These monitors are becoming affordable. We will have to ultimately reach some kind of compromise on the image sizes according to the plugin we use and according to predicted technology. -- LorenEvey - 23 May 2007
  • In layout four I was particulary interested in parents, children, and levels of subheadings. I hope that we can arrive at a TOC for the entire atlas that has predictable headings and subheadings across chapters. There is merit to considering having a chapter per topic page. In this case there would be 19 topic pages. Each chapter would have it's own TOC with local links. There would be consistancy across chapters. There would be an Introduction page to the entire atlas and a master TOC. You have probably seen the html help documents on the web. They go on forever and they are one page. I am not convinced that one page per chapter is the way to go but I think that doing it this way might simplify navigation. To a degree, we seem to be a bit chained to the current written atlas. Parts may have to be rearranged and rewritten to maximize the power of the WIKI format. I hope that we do not ultimately create an atlas that gives the impression of an "in house" document adpated to the WEB. -- LorenEvey - 23 May 2007
  • I think linking to the representative section for the summary table would be a good idea. We could list the slide label, or use the thumbnail itself (see what I did above and in TheKidneyL4 topic). This might save some space in the cells. Which do you prefer? -- AshleyLPistorio - 23 May 2007
  • OK, I trimmed it down. Now all that remains is a review section, with indexed subchapters... you can always go back to the prior version is you like it better. -- AshleyLPistorio - 23 May 2007
  • There's a lot of stuff on one page. Are you thinking to keep all of it here or are you thinking to break it down into chapters (I see you already made RenalCorpuscle4? )? If this is to stay here, we should make a direct link to start the atlas by chapter at the top of the TOC... for first time users to go through as they would in lab. The rest of this info is better for a review in one location (I think it's a little overwhelming for the first-timer?). -- AshleyLPistorio - 23 May 2007 Begin Topic
Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r12 < r11 < r10 < r9 < r8 | More topic actions
Archive.UrinarySystem4 moved from Main.UrinarySystem4 on 17 Jul 2007 - 06:17 by LorenEvey - put it back
 
Powered by TWiki
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback