showfed.php is showing relationhips that are not intended to be displayed.
| Project: | RUcore dlr/EDIT |
| Version: | 6.1 |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | chadmills |
| Status: | closed |
Jump to:
In sample object rutgers-lib:1743 3 relationships to other objects exist. One of those relationships, hasLicense, is being displayed when it shouldn't/ The @FOLLOW attribute is set to FALSE in the relationship listing through the relationship API.
<a href="http://rep-test.libraries.rutgers.edu/rucore/api/relationship/get/rutgers-lib:1743/" title="http://rep-test.libraries.rutgers.edu/rucore/api/relationship/get/rutgers-lib:1743/">http://rep-test.libraries.rutgers.edu/rucore/api/relationship/get/rutger...</a>
Only relationships with @FOLLOW=true should be displayed to the user.
Relationship API documentation reference on this topic:
<a href="http://rep-test.libraries.rutgers.edu/rucore/api/relationship/doc/#method-get" title="http://rep-test.libraries.rutgers.edu/rucore/api/relationship/doc/#method-get">http://rep-test.libraries.rutgers.edu/rucore/api/relationship/doc/#metho...</a>
I am not sure if this should be considered a 6.1 or 6.x issue at this time. However I am entering it as 6.1.
Comments
#1
#2
Fixed, please test.
To test you can visit this record in the public interface:
<a href="http://rep-devel.rutgers.edu/dlr/showfed.php?pid=rutgers-lib:1743" title="http://rep-devel.rutgers.edu/dlr/showfed.php?pid=rutgers-lib:1743">http://rep-devel.rutgers.edu/dlr/showfed.php?pid=rutgers-lib:1743</a>
You can then look at the XML for all the relationships here. You will see the relationship with the FOLLOW attribute set to FALSE. That one should not appear in the public display.
#3
#4
#5
Tested by creating a "License" relationship between two objects. "License" relationships are configured to not be FOLLOWED in the public display. I then looked up both records and neither showed the relationship existed. I then removed the relationship. This also tested the creation and deletion of relationships. I validated this using the Relationship API log feature.