Difference between revisions of "Talk:CURATEcamp DLF Ideas"

From CURATEcamp
Jump to: navigation, search
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
 
Some more ideas for discussion - feel free to do as you wish (Rick Fitzgerald, LOC)
 
Some more ideas for discussion - feel free to do as you wish (Rick Fitzgerald, LOC)
  
What types of routine data manipulation tasks would developers feel comfortable leaving to catalogers? What skill sets would catalogers need in order to do these tasks?
+
What types of data tasks would developers expect could be reasonably done by catalogers? What skill sets would catalogers need in order to do these tasks?
  
 
For those who have tried to move, even slightly, along the "continuum" from cataloger to developer, what were your experiences? What tools did you find most useful? Were you in a supportive atmosphere? What were some low-barrier "learn to code" environments that you found helpful?
 
For those who have tried to move, even slightly, along the "continuum" from cataloger to developer, what were your experiences? What tools did you find most useful? Were you in a supportive atmosphere? What were some low-barrier "learn to code" environments that you found helpful?
  
What are some of the best articulations out there by developers in dealing with "dirty" or difficult cataloging data, when parsing it out for a particular application? A typical example might include textual explanation of the process of parsing out a commonly found piece of data (a particular MARC field, normalizing a call number or identifier), alongside examples of the code used.
+
What are some of the best articulations out there by developers in dealing with "dirty" or difficult cataloging data, when parsing it out for a particular application? A typical example might include textual explanation of the process of parsing out a commonly found piece of data (a particular MARC field, normalizing a call number or identifier), alongside examples of the code used (see "[http://journal.code4lib.org/articles/3832]")

Latest revision as of 12:42, 2 November 2011

Some more ideas for discussion - feel free to do as you wish (Rick Fitzgerald, LOC)

What types of data tasks would developers expect could be reasonably done by catalogers? What skill sets would catalogers need in order to do these tasks?

For those who have tried to move, even slightly, along the "continuum" from cataloger to developer, what were your experiences? What tools did you find most useful? Were you in a supportive atmosphere? What were some low-barrier "learn to code" environments that you found helpful?

What are some of the best articulations out there by developers in dealing with "dirty" or difficult cataloging data, when parsing it out for a particular application? A typical example might include textual explanation of the process of parsing out a commonly found piece of data (a particular MARC field, normalizing a call number or identifier), alongside examples of the code used (see "[1]")