Login Respose

[Shamsh]

After sending login request to http://web.alitora.com/ASAPI_REST/asapi/0001/xml/login/cybernetikz1
With ($post="password=password&application=memomics_bio")
I get following xml as a result.
Here I get a tag named "resource ".Here is also no order of team
membership status or team ownership status.

* What does this tag mean?
* Is it dynamic? (depend on user)
* For what I need this tag value?

<results>
<statusCode>
<name>OK</name>
</statusCode>
<objects>
<memeUser>
<umis>Com.Memomics.AlitoraSystems.memomics.1155507</umis>
<name>Cyber Netikz</name>

<creatorUMIS>Com.Memomics.AlitoraSystems.system.1</creatorUMIS>
<categoryID>testnode</categoryID>
<creationDate>
<milis>1206985536000</milis>
</creationDate>
<numInteractionEdges>0</numInteractionEdges>
<numSubsumptionEdges>0</numSubsumptionEdges>

<ontologyVersion>1.0</ontologyVersion>
<ontologyID>test ontology id 1</ontologyID>
<ontologyURL>http://meme.net.ai</ontologyURL>
<scope>public</scope>
<segment>memomics</segment>
<version>1.0</version>

<loginID>cybernetikz1</loginID>
<email>ma...@alitora.com</email>
<affiliation>CyberNetikz</affiliation>
</memeUser>
<segment>
<create>false</create>
<read>true</read>

<update>false</update>
<segmentName>baseline</segmentName>
</segment>
<segment>
<create>true</create>
<read>true</read>
<update>true</update>

<segmentName>memomics</segmentName>
</segment>
<segment>
<create>true</create>
<read>true</read>
<update>true</update>
<segmentName>memomics_bio</segmentName>

</segment>
<session>
<sessionID>12071135469320.7659047294719498</sessionID>
</session>
<resource>
<resource>team-membership-14</resource>
</resource>
<resource>

<resource>team-ownership-9</resource>
</resource>
<resource>
<resource>create-vote</resource>
</resource>
<resource>
<resource>team-membership-6</resource>

</resource>
<resource>
<resource>team-membership-5</resource>
</resource>
<resource>
<resource>team-membership-17</resource>
</resource>
<resource>

<resource>team-membership-11</resource>
</resource>
<resource>
<resource>team-ownership-0</resource>
</resource>
<resource>
<resource>application.memomics_bio</resource>

</resource>
<resource>
<resource>download-file-annotation</resource>
</resource>
<resource>
<resource>team-membership-15</resource>
</resource>
<resource>

<resource>team-membership-2</resource>
</resource>
<resource>
<resource>messaging-access</resource>
</resource>
<resource>
<resource>team-membership-0</resource>

</resource>
<resource>
<resource>team-membership-13</resource>
</resource>
<resource>
<resource>team-ownership-2</resource>
</resource>
<resource>

<resource>segment.memomics.create</resource>
</resource>
<resource>
<resource>team-membership-4</resource>
</resource>
<resource>
<resource>team-ownership-6</resource>

</resource>
<resource>
<resource>team-membership-3</resource>
</resource>
<resource>
<resource>segment.memomics.read</resource>
</resource>
<resource>

<resource>team-membership-19</resource>
</resource>
<resource>
<resource>segment.memomics_bio.update</resource>
</resource>
<resource>
<resource>api-access</resource>

</resource>
<resource>
<resource>team-ownership-5</resource>
</resource>
<resource>
<resource>create-file-annotation</resource>
</resource>
<resource>

<resource>team-membership-12</resource>
</resource>
<resource>
<resource>team-ownership-7</resource>
</resource>
<resource>
<resource>segment.memomics.update</resource>

</resource>
<resource>
<resource>segment.memomics_bio.create</resource>
</resource>
<resource>
<resource>team-ownership-4</resource>
</resource>
<resource>

<resource>view-vote</resource>
</resource>
<resource>
<resource>api-transaction</resource>
</resource>
<resource>
<resource>annotation</resource>

</resource>
<resource>
<resource>team-access</resource>
</resource>
<resource>
<resource>segment.memomics_bio.read</resource>
</resource>
<resource>

<resource>team-ownership-8</resource>
</resource>
<resource>
<resource>segment.baseline.read</resource>
</resource>
<resource>
<resource>team-membership-9</resource>

</resource>
<resource>
<resource>team-membership-1</resource>
</resource>
<resource>
<resource>team-membership-8</resource>
</resource>
<resource>

<resource>team-membership-18</resource>
</resource>
<resource>
<resource>team-ownership-3</resource>
</resource>
<resource>
<resource>team-ownership-1</resource>

</resource>
<resource>
<resource>team-membership-16</resource>
</resource>
<resource>
<resource>team-membership-7</resource>
</resource>
<resource>

<resource>team-membership-10</resource>
</resource>
</objects>
</results>

[siaroslaw]

hello,
the result set is correct. Let me explain it in details.
The "resource" tags show which resources user has access to.
There are single resources like: "api-access", "create-vote" etc.
There are also so called 'quantitative' resources (for example "team-
membership-x"). Here, the maximum team membership is calculated as the
maximum x occured within these resources + 1 ,as we start counting
from 0. These resources are not sorted in ascending order beceause of
the nature of set.

So the resources 'de facto' determines the allowed maximum, they do
not state how many teams a user is memeber/owner of.
To check the teams user is assigned to, there is a "/teams" URI for
that.

Derek

[Marc Hadfield]

Hi Shamsh -

As Derek wrote, the resources define what functionality or data the user
has access to. This will change from user to user.

For example, your user account has access to the "annotation" resource
which means your user account is allowed to create annotations.

For your project, you can ignore these values.

To retrieve items in Memory, you use the "memory" REST API calls.
To retrieve a list of Teams, and the content of Teams, you use the
"team" REST API calls.

For your project you can first try to create a MemeDocument, add an
Annotation to the MemeDocument, and then put that in your user's
"memory". Once that works you can move to Teams and folders (we call
them "Topics").

Note: if your user did not have access to the "annotation" resource,
then attempting to create an annotation would fail with an error
message. Thus, the list of resources provided when you log in describes
what that user account can and cannot do.

Best,
Marc Hadfield

> </resource>

--
-------
Marc Hadfield
Alitora Systems
(917)991-9685
ma...@alitora.com
http://www.alitora.com

[Shamsh]

Thanks Marc.

On Apr 3, 9:04 pm, Marc Hadfield <m...@alitora.com> wrote:
> Hi Shamsh -
>
> As Derek wrote, the resources define what functionality or data the user
> has access to. This will change from user to user.
>
> For example, your user account has access to the "annotation" resource
> which means your user account is allowed to create annotations.
>
> For your project, you can ignore these values.
>
> To retrieve items in Memory, you use the "memory" REST API calls.
> To retrieve a list of Teams, and the content of Teams, you use the
> "team" REST API calls.
>
> For your project you can first try to create a MemeDocument, add an
> Annotation to the MemeDocument, and then put that in your user's
> "memory". Once that works you can move to Teams and folders (we call
> them "Topics").
>
> Note: if your user did not have access to the "annotation" resource,
> then attempting to create an annotation would fail with an error
> message. Thus, the list of resources provided when you log in describes
> what that user account can and cannot do.
>
> Best,
> Marc Hadfield
>
>
>
> Shamsh wrote:

> > After sending login request tohttp://web.alitora.com/ASAPI_REST/asapi/0001/xml/login/cybernetikz1

> > <email>m...@alitora.com</email>

> m...@alitora.comhttp://www.alitora.com

[Shamsh]

Thanks Derek