Should organization type say 'agent name'?

[nicolevasilevsky]

Shouldn't it say 'organization name'?

[marijane]

This is when you create an organization? How do you get to this screen? I don't know how to tell where it might be getting "Agent" from.

"Agent" is defined as the range for copyrightHolder (because I assumed a union wouldn't work based on the screenshots from yesterday) and it is the superclass for Organization and Person.

[nicolevasilevsky]

1. From here: https://alaska.dev.eagle-i.net/sweet
2. Click Create an organization
3. On this page, you can see agent name, agent type

[nicolevasilevsky]

Ah, if agent is the superclass for org or person, that explains why it is being displayed here. I am not sure if we should allow person as an option here, we didn't do that in eagle-i.

[marijane]

I agree, if you're clicking "create an organization", person shouldn't be here. I'm not sure what change needs to be made in the ontology, though, to fix this, because I'm not sure how it got here in the first place.

Is there a different place to create people? I want people to be createable instances so we can associate creators with their courses.

[nicolevasilevsky]

Yes, in eagle-i, people would be created in a different record. I think they always had to be associated with an org or a resource though, you couldn't just create a stand-alone person record.

[skcheng]

Yes, I think people can only be created as part of another resource. In our case, when creating a course, we should be able to click in the drop down next to creator and have an option to add new. This would create a stub for the person that can then be completed in the next step.

I'm wondering if part of the other issue with people is maybe we need another relationship besides creator? In the blink & eagle-i ontologies I think the relationships are things like provided_by, director_of, etc. See: https://search.eagle-i.net/model/#t=http://xmlns.com/foaf/0.1/Person&of=score.

Maybe creator is being reserved as metadata for creator of the record, e.g. whoever is entering the data. Does this ring any bells?

[pitviper6]

I think in regular old eagle-i, it's just person. we can add a title if we like but there aren't people sub classes. And yes, you have to create a person as a stub in an organization record.

On Fri, Dec 8, 2017 at 8:51 PM, Sophia notifications@github.com wrote:

Yes, I think people can only be created as part of another resource. In our case, when creating a course, we should be able to click in the drop down next to creator and have an option to add new. This would create a stub for the person that can then be completed in the next step.

I'm wondering if part of the other issue with people is maybe we need another relationship besides creator? In the blink & eagle-i ontologies I think the relationships are things like provided_by, director_of, etc. See: https://search.eagle-i.net/model/#t=http://xmlns.com/ foaf/0.1/Person&of=score.

Maybe creator is being reserved as metadata for creator of the record, e.g. whoever is entering the data. Does this ring any bells?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/NLightenGroup/nlighten-ontology/issues/12#issuecomment-350414767, or mute the thread https://github.com/notifications/unsubscribe-auth/APGpfr1wlYgnRR4TXH-O4Enp_mU5J1p7ks5s-eeUgaJpZM4Q7mXU .

[pitviper6]

Oh wait, but yes, there are classes of people! You create the stub as a PI, Director, contact person or other member. So for education resources, perhaps you'd want instructor and creator roles?

On Sat, Dec 9, 2017 at 4:48 PM, Juliane Schneider < juliane.schneider@gmail.com> wrote:

I think in regular old eagle-i, it's just person. we can add a title if we like but there aren't people sub classes. And yes, you have to create a person as a stub in an organization record.

On Fri, Dec 8, 2017 at 8:51 PM, Sophia notifications@github.com wrote:

Yes, I think people can only be created as part of another resource. In our case, when creating a course, we should be able to click in the drop down next to creator and have an option to add new. This would create a stub for the person that can then be completed in the next step.

I'm wondering if part of the other issue with people is maybe we need another relationship besides creator? In the blink & eagle-i ontologies I think the relationships are things like provided_by, director_of, etc. See: https://search.eagle-i.net/model/#t=http://xmlns.com/foaf/0. 1/Person&of=score.

Maybe creator is being reserved as metadata for creator of the record, e.g. whoever is entering the data. Does this ring any bells?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/NLightenGroup/nlighten-ontology/issues/12#issuecomment-350414767, or mute the thread https://github.com/notifications/unsubscribe-auth/APGpfr1wlYgnRR4TXH-O4Enp_mU5J1p7ks5s-eeUgaJpZM4Q7mXU .

[marijane]

The domain/range constraint additions on "provider" seems to have fixed this: