Navigation:
Documentation
Archive



Page Tree:

Child pages
  • Changing Technology

This wiki space contains archival documentation of Project Bamboo, April 2008 - March 2013.

Skip to end of metadata
Go to start of metadata

Changing Technology

Definition

This theme has been merged into Changing Technologies and Unsustainable Tools and is now closed for edits. Please make any further changes on that theme's page.

Technology change and obsolescence affects multiple levels of scholarly practice. An archive on floppy disks from 1995 is unusuable today if it hasn't been transferred to modern physical media and/or file formats. Every time a user upgrades their software, they have to change their process to accommodate changes in the software. How can scholars choose which technology to use for a long-term project, knowing that the technology will probably be outdated by the time they're finished?


 

Name(s)

Institution(s)

Proposed/originated by:

Quinn Dombrowski

University of Chicago

Current facilitator(s)

Facilitator_Name_Here_(optional)

Facilitator_Institution_Here_(optional)


Back to Identify Themes page...


What tools, standards, organizations, or efforts exist in this area of scholarly practice?

Item

Description - what is it?

URL or other reference

sound_byte_name_or_description (your_name)

summary_description (your_name)

http://www.interesting_thing.org


What tools, standards, organizations, or efforts are missing from this area of scholarly practice?

Item

Description - what is it?

URL or other reference

sound_byte_name_or_description (your_name)

summary_description (your_name)

http://www.interesting_thing.org


What part of this area of scholarly practice is within Project Bamboo scope, and why?

Item

Description - what is it?

Why is it in scope?

sound_byte_name_or_description (your_name)

summary_description (your_name)

explanation_of_why_in_scope (your_name)


What part of this area of scholarly practice is outside Project Bamboo scope, and why?

Item

Description - what is it?

Why is it out of scope?

sound_byte_name_or_description (your_name)

summary_description (your_name)

explanation_of_why_out_of_scope (your_name)


References

References (e.g., material from Workshop 1 notes or flipcharts)

Contributor

  •  What if the work that's been done doesn't run on supported hardware/software anymore? (Ex. 1 scribe notes, 1b-C)
  • Software changes ... one has invested in the "old" software ... learning something new becomes a burden and a barrier. So much time to invest in learning new software is a very serious disincentive to use. (Ex. 1 scribe notes, 1b-C)
  • Users change as well as technologies. (Ex. 1 scribe notes, 1c-A)
  • Difficult to decide on an abstract architecture when bottom-up tool development is moving (percolating) so quickly. What can facilitate quick and agile adoption of quickly developing tools. (Ex. 1 scribe notes, 1c-C)
  • A/V formats which go out of date need to be digitized and updated more often than print sources. (Ex. 4 scribe notes, 1c-B)
  • Wrong to see these things as built into a massive architecture that would then be used across the board.
    • Ultimately looking at obsolence too quickly. (Ex. 5 scribe notes, 1c-B)

Quinn Dombrowski

Back to Identify Themes page...