[CSDb] - User Forums - Discrepancy between XML-data and group page data

You are not logged in - nap

CSDb User Forums

Forums > CSDb Bug Reports > Discrepancy between XML-data and group page data

2019-07-08 21:48

Mr.Ammo
Account closed

Registered: Oct 2002
Posts: 228

Discrepancy between XML-data and group page data

I noticed a discrepancy in the data served by the web services and the data presented on the web page.

An example:
When I go to the group page of No Name I it will show that there are a total of 62 (ex-)members based on handles.

When I load the XML of the webservice using this URL: https://csdb.dk/webservice/?type=group&id=1&depth=2, the API will serve 63 members. That means that there's 1 extra member field in the XML, but it has no handle ID or any other identifiable data.

For this extra member-field it gives the following data:

<Member>
  <Profession>Diskmag Editor</Profession>
  <Status>ex</Status>
</Member>

This discrepancy can mean two things:

1) the No Name page is incomplete and should show this diskmag editor
2) this diskmag editor does not exist and should not be included in the XML data the API serves.

What is the truth? If 1 is the truth, then both the group page and the XML-data are incomplete. If 2 is the truth, then this diskmag editor should not be included in the XML-data.

It would be nice that this gets fixed so that that API/web service can be 100% trusted and we don't need to make guesses and create work-arounds to process the data.

2019-07-20 01:16

Mr.Ammo
Account closed

Registered: Oct 2002
Posts: 228

Here's another example:

It concerns Laxity. The group page returns 50 members. The web service XML returns a total of 56 members. Like in the above example, the XML (https://csdb.dk/webservice/?type=group&id=145&depth=2) returns 6 extra 'members' and they do not have a //CSDbData/Group/Member/Handle/ID.

The extra's which it returns are the following:

<Member>
    <Profession>Cracker</Profession>
    <Status>ex</Status>
</Member>
[...]
<Member>
    <Profession>Coder</Profession>
    <Profession>Graphician</Profession>
    <Status>ex</Status>
</Member>
[...]
<Member>
    <Profession>Coder</Profession>
    <Profession>Cracker</Profession>
    <Profession>Original Supplier</Profession>
    <JoinYear>1993</JoinYear>
    <LeaveYear>1994</LeaveYear>
    <Status>ex</Status>
</Member>
[...]
<Member>
    <Profession>Coder</Profession>
    <JoinMonth>11</JoinMonth>
    <JoinYear>1997</JoinYear>
    <LeaveYear>1998</LeaveYear>
    <Status>ex</Status>
</Member>

This could be the member NIC, he has the same profession and join date and leave year. But he already has a complete member record in the XML:

<Member>
    <Handle>
    <ID>7033</ID>
    <Handle>NIC</Handle>
        <Scener>
            <ID>6464</ID>
            <Country>Germany</Country>
            <Handles>
                <Handle>
                    <ID>7033</ID>
                </Handle>
            </Handles>
        </Scener>
    </Handle>
    <Profession>Coder</Profession>
    <JoinMonth>11</JoinMonth>
    <JoinYear>1997</JoinYear>
    <LeaveYear>1998</LeaveYear>
    <Status>ex</Status>
</Member>

And the others:

[...]
<Member>
    <Profession>Coder</Profession>
    <Profession>Cracker</Profession>
    <Status>ex</Status>
</Member>
[...]
<Member>
    <Profession>Cracker</Profession>
    <Profession>Original Supplier</Profession>
    <Profession>Swapper</Profession>
    <JoinYear>1991</JoinYear>
    <LeaveYear>1994</LeaveYear>
    <Status>ex</Status>
</Member>

If you guys need more examples, I can try and find more of them.

2022-05-14 17:41

instant

Registered: Mar 2020
Posts: 20

Old thread but I'm seeing the same thing.

I'm guessing that the first record is element 0 of the array and it seems that it is just empty and returning the last used values for "Profession" and "Status" variables.

Here are the inconsistencies I've found. Maybe this will help to resolve the issue.

O'Dog - Handle ID 11316 - Member Record 1, 15
Manik - Handle ID 1762 - Member Record 3, 35

Member Record 14 - No Handle ID

Member Record 15 - Same Handle ID as #1 but incomplete data

Member Record 18 - No Handle ID
Member Record 23 - No Handle ID
Member Record 28 - No Handle ID

Member Record 25 - Same Handle ID as #3 but incomplete data

Member Record 37 - No Handle ID

Member Record 38 - Handle ID is referenced in Member Record 9 in Scener data as a previous handle, incomplete data

Member Record 43 - Handle ID is referenced in Member Record 17 in Scener data as a previous handle, incomplete data

Member Record 48 - Handle ID is referenced in Member Record 9 in Scener data as a previous handle, incomplete data

Member Record 54 - Handle ID is referenced in Member Record 53 in Scener data as a previous handle, incomplete data

I'm happy to help fix this issue with the webservice. I've found some other issues that I could take care of too.
Who should I talk to about getting involved?

2022-05-14 17:55

instant

Registered: Mar 2020
Posts: 20

The number of "active" member records is the same as the number of records with no Handle ID. Not sure if that is connected but something to look at.

Also, other than record 0, there are 4 good records between each bad record.

Refresh

Subscribe to this thread: