Serving readers as best as possible: splitting repair reports

St. Clair Beach Solitude

D
St. Clair Beach Solitude

  • 5
  • 2
  • 40
Reach for the sky

H
Reach for the sky

  • 3
  • 4
  • 71
Agawa Canyon

A
Agawa Canyon

  • 3
  • 2
  • 120
Frank Dean,  Blacksmith

A
Frank Dean, Blacksmith

  • 13
  • 8
  • 310

Recent Classifieds

Forum statistics

Threads
198,867
Messages
2,782,213
Members
99,735
Latest member
tstroh
Recent bookmarks
0

Andreas Thaler

Subscriber
Joined
Nov 19, 2017
Messages
4,863
Location
Vienna/Austria
Format
35mm
Once again I am thinking about my repair reports here and how I can best write them.

I am trying to put myself in the position of two fictitious readers:
  1. Reader A wants concise and easy-to-read information on how to solve a problem. He is less interested in details and background than in a quick way to solve the problem, preferably as a tutorial.
  2. Reader B is more interested in analyzing the problem and the details of how to solve it. In return, he is prepared to read longer texts.
Serving both readers in one article in such a way that they are satisfied is almost impossible.

For one, it is too dense and too long, for the other, too reduced.


Feedback gained

I noticed that when I started my repair reports in November last year, I received a lot of feedback, resulting in interesting discussions, which then decreased over time.

Apparently, my readers were initially still willing to read longer texts. Or the reports had a density and length that was acceptable to everyone.

This shows me that I need to change something here.


Views as a guide

I can tell whether my reports are popular by the views indicated in the forum topic overview. These should be internal and external readers who find my articles via Google, for example.

From this I try to get an idea of which reports are of interest and which are less so. Are these longer or shorter articles, or ones on specific topics?

Since I am always learning new things myself, the information I want to convey is also increasing.


Splitting reports

I will therefore now split my reports into two independent parts:
  • the problem description and analysis will be the first post and
  • the attempt to solve the problem will be the second post.
Both reports belong together and I will link them, so that every reader interested in the topic can find what interests them.

I am curious to see how this will be received 🙃
 
Last edited:
OP
OP

Andreas Thaler

Subscriber
Joined
Nov 19, 2017
Messages
4,863
Location
Vienna/Austria
Format
35mm
You see, I can't escape my previous job as a public relations worker.

I had always to worry about conveying information, not just the content 😌
 
OP
OP

Andreas Thaler

Subscriber
Joined
Nov 19, 2017
Messages
4,863
Location
Vienna/Austria
Format
35mm
Within the same thread, please. Please do keep everything that belongs to the same project/problem within the same thread.

At some point we could also start to organize all posts in the repair forum (not just mine, of course) by topic.

But I wonder whether that makes sense, apart from the work, also for the constant updating.

The search function in the forum is perfect and external people, i.e. non-members, can also find posts very easily via Google.
 

koraks

Moderator
Moderator
Joined
Nov 29, 2018
Messages
22,932
Location
Europe
Format
Multi Format
At some point we could also start to organize all posts in the repair forum (not just mine, of course) by topic.

We're always open to suggestions.

Having said that, there's also always a tension between the desire to keep the number of subforums to a minimum, or to further split out content by adding subforums on the other hand. The net result is that we've kept it pretty much the way it is for the past couple of years.

One possibility to suit everyone's tastes would be to tag threads, which would allow people to browse by tag as well as by subforum. However, tagging involves quite a bit of manual intervention and a good dose of discipline, and the discussion on which subforums are appropriate would simply shift to which tags we should(n't) have. Btw, this idea has also been discussed a bit in the past, but there's no very strong force to promote it. For the most part, I'm inclined to say that things work fairly well as they are.
 
OP
OP

Andreas Thaler

Subscriber
Joined
Nov 19, 2017
Messages
4,863
Location
Vienna/Austria
Format
35mm
Thank you @koraks

I think that the work of writing repair reports is worthwhile, as interest in analogue photography is increasing, as confirmed by dealers and specialist laboratories at least here in Vienna.

At the same time, however, the number of people who learned how to repair cameras, ideally from the manufacturer, is decreasing.

And since there are no new cameras for photography (that can replace the old ones), service is needed.
 

miha

Member
Joined
Feb 15, 2007
Messages
2,962
Location
Slovenia
Format
Multi Format
Certainly. Your efforts and those of all others who document their findings are very valuable for anyone picking up a camera to repair it.

My thoughts exactly. And some of us were enjoying extra privileges from @Andreas Thaler 's expertise 😃
 
Photrio.com contains affiliate links to products. We may receive a commission for purchases made through these links.
To read our full affiliate disclosure statement please click Here.

PHOTRIO PARTNERS EQUALLY FUNDING OUR COMMUNITY:



Ilford ADOX Freestyle Photographic Stearman Press Weldon Color Lab Blue Moon Camera & Machine
Top Bottom