Hhinsch Week 3 - Revision history

Hhinsch: changed my references so you can see the w3sschools website i used without clicking on the link

2017-09-20T06:40:54Z

changed my references so you can see the w3sschools website i used without clicking on the link

Hhinsch: added my electronic notebook page

2017-09-20T06:24:09Z

added my electronic notebook page

Hhinsch: changed the font of my identifiers

2017-09-20T05:34:34Z

changed the font of my identifiers

Hhinsch: changed the references a bit(the formatting of the link to the dynamic text processing page)

2017-09-20T05:33:01Z

changed the references a bit(the formatting of the link to the dynamic text processing page)

Hhinsch: i edited my references section

2017-09-20T05:31:38Z

i edited my references section

Hhinsch: I added a references and acknowledgements section as well as edited the sequence of commands that extracts just the answers

2017-09-20T05:30:09Z

I added a references and acknowledgements section as well as edited the sequence of commands that extracts just the answers

Hhinsch: added the sequence of commands that extracts just the answers

2017-09-20T05:18:23Z

added the sequence of commands that extracts just the answers

Hhinsch: edited my first and second answers

2017-09-20T05:15:30Z

edited my first and second answers

Hhinsch: edited answer 1 with another internal link

2017-09-20T04:45:30Z

edited answer 1 with another internal link

Hhinsch: deleted irrelevant text

2017-09-20T04:24:33Z

deleted irrelevant text

@@ Line 41: / Line 41: @@
 #I used the [[Dynamic Text Processing]] page to get a firmer grasp on using sed.
 #I used [[The Web from the Command Line]] page to get a firmer grasp on curl.
-#I used [https://www.w3schools.com/tags/tag_div.asp this] web developer site to find identifiers in the code.
+#I used [https://www.w3schools.com/tags/tag_div.asp this] web developer site(<code>https://www.w3schools.com/tags/tag_div.asp</code>) to find identifiers in the code.
 #I used the [[Week 3]] assignment page: <code>https://xmlpipedb.cs.lmu.edu/biodb/fall2017/index.php/Week_3</code> multiple times to clarify the questions being asked and to access the pages mentioned above.
 {{Template:hhinsch}}

@@ Line 31: / Line 31: @@
 ===The sequence of commands that extracts “just the answers” from the raw-data response===
 <code>curl "http://web.expasy.org/cgi-bin/translate/dna_aa?pre_text=cgatggtacatggagtccagtagccgtagtgatgagatcgatgagctagc&output=Verbose&code=Standard" | grep -E '<(BR|PRE)>' | sed 's/<[^>]*>//g'</code>
+===Electronic Notebook===
 ===Acknowledgements===
 #I worked with both [[User:ebachour|Eddie Bachoura]] and [[User:Zvanysse|Zachary Van Ysseldyk]] in person and over text to collaborate and come up with my answers.

@@ Line 12: / Line 12: @@
 #Yes there are links to other pages within the ExPASy translation server's responses. <code>/css/sib_css/sib.css</code> <code>/css/sib_css/sib_print.css</code> and <code>/css/base.css</code> are some of the links to other pages within the ExPASy translation server which take care of the visual aspect of the page. There are some other links to other servers that complete different operations.
 #I noticed a few identifiers:
 *id='sib_top'
 *id='sib_container'
@@ Line 25: / Line 26: @@
 *id = "sib_footer_right"
 *id = "sib_footer_gototop"
 These serve as small descriptions of what is being identified, for example: id="sib_expasy_logo" is identifying the eXPASy logo.
 ===The sequence of commands that extracts “just the answers” from the raw-data response===

@@ Line 37: / Line 37: @@
 ===References===
-#I used [[Dynamic Text Processing|this]] dynamic text processing page to get a firmer grasp on using sed.
+#I used the [[Dynamic Text Processing]] page to get a firmer grasp on using sed.
 #I used [[The Web from the Command Line]] page to get a firmer grasp on curl.
 #I used [https://www.w3schools.com/tags/tag_div.asp this] web developer site to find identifiers in the code.

@@ Line 40: / Line 40: @@
 #I used [[The Web from the Command Line]] page to get a firmer grasp on curl.
 #I used [https://www.w3schools.com/tags/tag_div.asp this] web developer site to find identifiers in the code.
-#I used the [[Week 3]] assignment page multiple times to clarify the questions being asked and to access the pages mentioned above.
+#I used the [[Week 3]] assignment page: <code>https://xmlpipedb.cs.lmu.edu/biodb/fall2017/index.php/Week_3</code> multiple times to clarify the questions being asked and to access the pages mentioned above.
 {{Template:hhinsch}}

← Older revision		Revision as of 05:30, 20 September 2017
Line 30:		Line 30:
	===The sequence of commands that extracts “just the answers” from the raw-data response===		===The sequence of commands that extracts “just the answers” from the raw-data response===
	<code>curl "http://web.expasy.org/cgi-bin/translate/dna_aa?pre_text=cgatggtacatggagtccagtagccgtagtgatgagatcgatgagctagc&output=Verbose&code=Standard" \| grep -E '<(BR\|PRE)>' \| sed 's/<[^>]*>//g'</code>		<code>curl "http://web.expasy.org/cgi-bin/translate/dna_aa?pre_text=cgatggtacatggagtccagtagccgtagtgatgagatcgatgagctagc&output=Verbose&code=Standard" \| grep -E '<(BR\|PRE)>' \| sed 's/<[^>]*>//g'</code>
		+
		+	===Acknowledgements===
		+	#I worked with both [[User:ebachour\|Eddie Bachoura]] and [[User:Zvanysse\|Zachary Van Ysseldyk]] in person and over text to collaborate and come up with my answers.
		+	#[[User:Zvanysse\|Zachary Van Ysseldyk]] helped me after class to utilize the sed and grep commands in order to eliminate the unwanted code.
		+	#While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.[[User:Hhinsch\|Hhinsch]] ([[User talk:Hhinsch\|talk]]) 22:30, 19 September 2017 (PDT)
		+
		+	===References===
		+	#I used [[Dynamic Text Processing\|this]] dynamic text processing page to get a firmer grasp on using sed.
		+	#I used [[The Web from the Command Line]] page to get a firmer grasp on curl.
		+	#I used [https://www.w3schools.com/tags/tag_div.asp this] web developer site to find identifiers in the code.
		+	#I used the [[Week 3]] assignment page multiple times to clarify the questions being asked and to access the pages mentioned above.
		+
		+	{{Template:hhinsch}}

← Older revision		Revision as of 05:18, 20 September 2017
Line 26:		Line 26:
	*id = "sib_footer_gototop"		*id = "sib_footer_gototop"
	These serve as small descriptions of what is being identified, for example: id="sib_expasy_logo" is identifying the eXPASy logo.		These serve as small descriptions of what is being identified, for example: id="sib_expasy_logo" is identifying the eXPASy logo.
		+
		+
		+	===The sequence of commands that extracts “just the answers” from the raw-data response===
		+	<code>curl "http://web.expasy.org/cgi-bin/translate/dna_aa?pre_text=cgatggtacatggagtccagtagccgtagtgatgagatcgatgagctagc&output=Verbose&code=Standard" \| grep -E '<(BR\|PRE)>' \| sed 's/<[^>]*>//g'</code>

← Older revision		Revision as of 05:15, 20 September 2017
Line 10:		Line 10:

	===Answers to the two questions regarding the ExPASy translation server’s output===		===Answers to the two questions regarding the ExPASy translation server’s output===
−	#Yes there are links to other pages within the ExPASy translation server's responses. <code>/css/sib_css/sib.css</code> <code>/css/sib_css/sib_print.css</code> and <code>/css/base.css</code> are some of the links to other pages within the ExPASy translation server which take care of the visual aspect of the page.	+	#Yes there are links to other pages within the ExPASy translation server's responses. <code>/css/sib_css/sib.css</code> <code>/css/sib_css/sib_print.css</code> and <code>/css/base.css</code> are some of the links to other pages within the ExPASy translation server which take care of the visual aspect of the page. There are some other links to other servers that complete different operations.
		+	#I noticed a few identifiers:
		+	*id='sib_top'
		+	*id='sib_container'
		+	*id='sib_header_small'
		+	*id="sib_expasy_logo"
		+	*id="sib_link"
		+	*id="expasy_link"
		+	*id='resource_header'
		+	*id='sib_header_nav'
		+	*d='sib_body'
		+	*id = 'sib_footer'
		+	*id = 'sib_footer_content'
		+	*id = "sib_footer_right"
		+	*id = "sib_footer_gototop"
		+	These serve as small descriptions of what is being identified, for example: id="sib_expasy_logo" is identifying the eXPASy logo.

← Older revision		Revision as of 04:45, 20 September 2017
Line 10:		Line 10:

	===Answers to the two questions regarding the ExPASy translation server’s output===		===Answers to the two questions regarding the ExPASy translation server’s output===
−	#Yes there are links to other pages within the ExPASy translation server's responses. <code>/css/sib_css/sib.css</code> ~~is one of them which links to the style of what we are seeing on the actual webpage~~. <code>/css/base.css</code> ~~is another~~ which ~~I believe would~~ take care of the ~~text~~.	+	#Yes there are links to other pages within the ExPASy translation server's responses. <code>/css/sib_css/sib.css</code> <code>/css/sib_css/sib_print.css</code> and <code>/css/base.css</code> are some of the links to other pages within the ExPASy translation server which take care of the visual aspect of the page.

← Older revision		Revision as of 04:24, 20 September 2017
Line 10:		Line 10:

	===Answers to the two questions regarding the ExPASy translation server’s output===		===Answers to the two questions regarding the ExPASy translation server’s output===
−	#Yes there are links to other pages within the ExPASy translation server's responses. <code>/css/sib_css/sib.css</code> is one of them which links to the style of what we are seeing on the actual webpage. <code>/css/base.css</code>~~/css/base.css~~ is another which I believe would take care of the text.	+	#Yes there are links to other pages within the ExPASy translation server's responses. <code>/css/sib_css/sib.css</code> is one of them which links to the style of what we are seeing on the actual webpage. <code>/css/base.css</code> is another which I believe would take care of the text.