Possible content server changes (@starson17)

[chaley]

After our discussion about the OPDS server, I made some changes to the normal and mobile content servers. I haven't yet submitted these changes to Kovid because I wanted to check to see if they are useful.

I added custom field values to both servers. The result is similar for both, so I will show the mobile one here. The text shown for one book with several custom fields is below. The output does not contain <br> elements, so it wraps wherever the browser wants to wrap it.

1632 [1632 - 1] by Flint, Eric - 768.5 KB - 2010/01/05 23:00:00
Tags=[Alternate history,SRC:BaenFree,foobar,a,c,b,e,d,g,f,ffff1] Another Date=[00] 
My Bool=[Yes] My Date=[2010-Jan-21] My Float=[1.0] My Int=[2] My Rating=[2] 
My Series=[SomeSeries [4]] My Text=[flapper] Text Multiple=[9, 8, 5, 6]

Is this helpful? Should it be changed in some (possible) way?

[Starson17]

Originally Posted by chaley

After our discussion about the OPDS server, I made some changes to the normal and mobile content servers. I haven't yet submitted these changes to Kovid because I wanted to check to see if they are useful.

Yes, they are useful. Very useful! I know what custom fields I've added, and their format, but family does not. I have to leave little messages in index.html for the content server with recommended searches to find, e.g. books with literary awards, then they ask me where they can see which award and what year. Mobile and normal can both use this treatment.

The output does not contain <br> elements, so it wraps wherever the browser wants to wrap it.

That's exactly what I would recommend.

1632 [1632 - 1] by Flint, Eric - 768.5 KB - 2010/01/05 23:00:00
Tags=[Alternate history,SRC:BaenFree,foobar,a,c,b,e,d,g,f,ffff1] Another Date=[00] 
My Bool=[Yes] My Date=[2010-Jan-21] My Float=[1.0] My Int=[2] My Rating=[2] 
My Series=[SomeSeries [4]] My Text=[flapper] Text Multiple=[9, 8, 5, 6]

Is this helpful? Should it be changed in some (possible) way?

As usual, it's easier to make suggestions after some hands-on interaction, but it looks good to me as-is. If you decide to set up a separate source branch, for testing, let me know, but I doubt it needs it. Any tweaking that might occur later should be easy to do without much disruption I can see.

I'm still in the middle of adding data to some new custom fields, but I was close to looking at some way to do this myself. Thanks!

On a related note, the multiple field new search term tweak is working well. I have a new multisearch term of Awards that searches custom series-like fields #award1 and #award2.

For reasons unrelated to the tweak, I've found that if I know there's an overlap (e.g. Nebula and Hugo), it works best to try to keep all of the Hugos and Hugo Nominated in #award1 and all the Nebula related awards in #award2.

[chaley]

I pushed the changes to Kovid for his perusal/approval. As the changes are very similar to what he already approved for the OPDS version, I don't expect a long or complicated cycle.

[chaley]

Code is in the trunk release. Kovid asked me to by default limit the number of tags displayed for the standard and custom tags fields to 5. A tweak exists to change that number, should someone want to.

[Starson17]

Originally Posted by chaley

Code is in the trunk release. Kovid asked me to by default limit the number of tags displayed for the standard and custom tags fields to 5. A tweak exists to change that number, should someone want to.

I'll test it when I get access to my main content server. Again, thanks!

[Starson17]

Originally Posted by Starson17

I'll test it when I get access to my main content server. Again, thanks!

It works great!